Merged
Conversation
Contributor
|
Tagging subscribers to this area: @agocke, @dotnet/gc |
Member
|
/azp run runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Member
|
/azp run runtime-coreclr gcstress-extra |
|
Azure Pipelines successfully started running 1 pipeline(s). |
mangod9
approved these changes
Feb 19, 2026
Contributor
|
Any chance this will be included in milestone "10.0.4" ? |
Member
|
/ba-g all failures are known |
Member
|
@snakefoot There's a chance 😀. Have to make sure it won't hold anything up |
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
3 participants
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 #123966 to release/10.0
/cc @agocke
Customer Impact
Customer reported that they saw GC deadlocks after upgrading to .NET 10. This PR is the cause. After revert, deadlocks went away.
Regression
Testing
A private build was shared with the customer and confirmed that this PR was the cause of the regression.
Risk
Low. This will return us to the .NET 9 state. This PR was intended to work around issues with high pinning scenarios, but the previous state was well-understood and acceptable.