[NativeAOT] Object synchronization method was called from an unsynchronized block of code

[MichalStrehovsky]

Unhandled exception. System.Threading.SynchronizationLockException: Object synchronization method was called from an unsynchronized block of code.
   at System.Threading.Monitor.Exit(Object) + 0x170
   at System.Runtime.CompilerServices.ConditionalWeakTable`2.Container.Finalize() + 0xdc
   at System.Runtime.__Finalizer.DrainQueue() + 0x4c
   at System.Runtime.__Finalizer.ProcessFinalizers() + 0x8c

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=868709
Build error leg or test failing: System.Runtime.Tests.WorkItemExecution
Pull request: #109772

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": ["SynchronizationLockException", "System.Threading.Monitor.Exit(Object) + 0x"],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=868709
Error message validated: [SynchronizationLockException System.Threading.Monitor.Exit(Object) + 0x]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/13/2024 9:38:22 PM UTC

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

[jkotas]

This was assumed to be fixed by #104340 , but it does not appear to be the case.

cc @VSadov

[VSadov]

The other issues was causing similar crashes in ilc, but was not observed to fail tests (or just was too rare in tests).
This is a test failure, so could be potentially a different issue.

[jeffschwMSFT]

removing blocking-clean-ci as this issue has not been hit in 30 days

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0