Skip to content

Avoid GC transition during allocator fatal errors - #135580

Draft
tommcdon wants to merge 3 commits into
dotnet:mainfrom
tommcdon:dev/tommcdon/executable-allocator-fatal-error-deadlock
Draft

tommcdon wants to merge 3 commits into
dotnet:mainfrom
tommcdon:dev/tommcdon/executable-allocator-fatal-error-deadlock

Conversation

@tommcdon

Copy link
Copy Markdown
Member

Preserve the preallocated last-thrown exception handle for debugger reporting when the executable allocator invokes fatal error handling from preemptive mode.

Preserve the preallocated last-thrown exception handle for debugger reporting when the executable allocator invokes fatal error handling from preemptive mode.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Defer MapRW fatal error reporting until after releasing the allocator lock so GC write-barrier updates can complete. Add a deterministic regression that establishes both sides of the GC/JIT deadlock.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep the servicing fix limited to RW mapping and metadata allocation failures. Inject failures through the real handlers, coordinate the first full GC without competing JIT work, and restrict the regression to supported Checked configurations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant