[release/10.0] Fix array size overflow in objectalloc.cpp - #132485
Merged
Conversation
Fixes #123361 The CI probably won't be happy to run the test repro
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
EgorBo
approved these changes
Aug 18, 2026
steveisok
enabled auto-merge (squash)
August 20, 2026 16:18
Member
|
/ba-g Unrelated known issue. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #123362 to release/10.0
/cc @AndyAyersMS @EgorBo
Customer Impact
Reported in #132480 and #123361
Regression
New functionality in .NET 10 (#112250). Class layout computations for very large known-sized arrays could overflow. Done as part of assessing the array for stack allocation.
Testing
Verifed it fixes the repros from both issues.
Risk
Low, avoids trying to compute a layout for a stack allocation that can never happen.