-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[release/7.0] Crash when region survives >2GB #80392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Tagging subscribers to this area: @dotnet/gc |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this actually doesn't look like it has most of the fix, for example, the part where it changes int to size_t for the survived field?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
approved. we will take for consideration in 7.0.x
Thanks for the review! This PR is now ready and has been tested by confirming:
|
Failures don't look related to the changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Approved by Tactics (7.0.3). |
Backport of #80302 that fixes #79486
Customer Impact
The impact of this bug is constrained to users who have very large LOH segments where one segment survives more than 2GB - leading to a crash.
Testing
We were able to test locally after consistently repro'ing the issue and proved that the fix took care of the bug.
Risk
Low risk change since it fixes the semantics of a type that was meant to be unsigned (from an int).