Repository navigation
[release/11.0] Fix software EH memory leak on Unix - #135541
Merged
JulieLeeMSFT merged 1 commit intoOct 12, 2026
Merged
Conversation
Backport of dotnet#135290, including dotnet/runtime@4d1b425 to skip the regression test where working-set monitoring is unsupported. The CoreCLR change is adapted to the GCX_COOP scope used on release/11.0. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9fe58a3a-d045-4e26-af87-9b85acdea60d
|
Azure Pipelines: Successfully started running 3 pipeline(s). 13 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @agocke |
jkotas
approved these changes
Oct 9, 2026
This was referenced Oct 10, 2026
Member
|
/ba-g known issues. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #135290 to release/11.0
/cc @janvorli
Customer Impact
There is a memory leak of
CONTEXTandEXCEPTION_RECORDdata structures on Unix (about 3400 bytes on amd64) when theDispatchManagedExceptionfor software managed exceptions thrown from native runtime code is executed. The managed exception handling is not taking ownership of the context and exception records in cases they were dynamically allocated.Regression
Testing
Coreclr and libraries tests, directed test for the issue that was added with the fix
Risk
Low, it changes software exception handling to the same plan as was always there for hardware exception handling w.r.t. to the ownership of the contexts.