[release/8.0-staging] [mono] Fix class initialization spurious wakeups #96905
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 #96903 to release/8.0-staging
/cc @lambdageek
Customer Impact
Customers running multi-threaded code on mobile platforms may experience crashes at startup or during class initialization. In particular if multiple threads try to call the static constructor for the same type at the same time, the runtime may assert.
Related to #96872 and #96804
This is a regression in .NET SDK 8.0.1 due to #93943
Testing
Manual testing.
Risk
Low.
IMPORTANT: If this backport is for a servicing release, please verify that:
The PR target branch is
release/X.0-staging
, notrelease/X.0
.If the change touches code that ships in a NuGet package, you have added the necessary package authoring and gotten it explicitly reviewed.