Uh oh!
There was an error while loading. Please reload this page.
[release/8.0] Properly handle debugger-enumerating interior pointers and enregistered refs - #92360
Conversation
ghost
commented
Sep 20, 2023
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. |
jeffschwMSFT
left a comment
There was a problem hiding this comment.
approved. we will take for consideration in RC2
aa578e3 to
1ac5733Compare
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.