-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NativeAOT tests crashing with infinite recursion in Lock #94227
Comments
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas Issue Detailslog and dump for System.Runtime.Extensions.Tests: https://dev.azure.com/dnceng-public/public/_build/results?buildId=456483&view=ms.vss-test-web.build-test-results-tab&runId=10276056&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=150703
|
cc @kouvel |
Introduced by #87672 |
- The `Monitor` type was being constructed due to the use of `Monitor.DebugBlockingScope`, added that to the initialization phase - If necessary, an alternative may be to move `DebugBlockingScope` to be under `Lock`. Based on the comments the thread-static field is apparently bound-to in debugging scenarios. - Fixes dotnet#94227
* Fix class construction recursion issue in `Lock` on NativeAOT - The `Monitor` type was being constructed due to the use of `Monitor.DebugBlockingScope`, added that to the initialization phase - If necessary, an alternative may be to move `DebugBlockingScope` to be under `Lock`. Based on the comments the thread-static field is apparently bound-to in debugging scenarios. - Fixes #94227 * Remove `DebugBlockingScope` instead
log and dump for System.Runtime.Extensions.Tests: https://dev.azure.com/dnceng-public/public/_build/results?buildId=456483&view=ms.vss-test-web.build-test-results-tab&runId=10276056&paneView=dotnet-dnceng.dnceng-build-release-tasks.helix-test-information-tab&resultId=150703
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: