Uh oh!
There was an error while loading. Please reload this page.
Check if External Object Context is still active after a possible GC - #59285
Conversation
AaronRobinsonMSFT
commented
Sep 18, 2021
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1247477775 |
Check if `IsActive()` during consideration too.
Use detach state instead of IsActive state for EOC.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Co-authored-by: Elinor Fung <elfung@microsoft.com>
Co-authored-by: Elinor Fung <elfung@microsoft.com>
davidwrighton
commented
Sep 21, 2021
This change relies on this AllocateObjectArray call not triggering multiple GCs. While I think that such behavior would be unusual, I don't think its a good practice to rely on such a detail. Refers to: src/coreclr/vm/interoplibinterface_comwrappers.cpp:355 in e820da6. [](commit_id = e820da6, deletion_comment = False) |
Uh oh!
There was an error while loading. Please reload this page.
davidwrighton
left a comment
There was a problem hiding this comment.
The allocation problem here now looks solved.
…59285) * Handle a possible GC after allocating an array by iterating over the hash again. Co-authored-by: Elinor Fung <elfung@microsoft.com>
AaronRobinsonMSFT
commented
Sep 21, 2021
/backport to release/6.0-rc2 |
Started backporting to release/6.0-rc2: https://github.com/dotnet/runtime/actions/runs/1259570246 |
Comments in this code detail the logic and reasons for failure.
This should be considered for .NET 6.
Fixes#59072
/cc @davidwrighton@jkoritzinsky@elinor-fung