-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[release/8.0] Properly handle debugger-enumerating interior pointers and enregistered refs #92360
[release/8.0] Properly handle debugger-enumerating interior pointers and enregistered refs #92360
Conversation
Tagging subscribers to this area: @tommcdon Issue DetailsBackport of #92313 to release/8.0 Customer ImpactTestingRiskIMPORTANT: If this backport is for a servicing release, please verify that:
|
The change to It seems like the right change long term for .Net 9 though. |
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 RC2
aa578e3
to
1ac5733
Compare
Backport of #92313 to release/8.0
/cc @hoyosjs @leculver
Customer Impact
Due to a rewrite of enumeration logic, users of ICorDebug will see long standing bugs surface more often than before. Now, users would get silently incomplete heap reports as the walks are halted eagerly on errors.
Testing
Manual testing of simple scenarios. Waiting on results from more thorough testing.
Risk
Low - debugger enumeration only scenarios. Lock usage may raise the risk, but it's a reliability issue that reflect on an assert when running canonical debugger scenarios.