-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Critical section level violation in Interop codebase #44114
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
failed again in job: runtime-coreclr crossgen2-composite 20201103.1 failed test: Interop\PInvoke\Delegate\DelegateTest\DelegateTest.cmd R2R-CG2 windows x86 Checked @ Windows.10.Amd64.Open Error message
|
|
|
Failed in #44688 |
I was unable to reproduce this locally. I tried all the above tests using the various |
Description
Critical section level order violation in interop codebase. Code in
DispatchInfo::SynchWithManagedView
takes a lock of level CrstInterop but then calls into managed code which may implicitly triggerCrstPendingTypeLoadEntry
. While this may not repro consistently, this is a bug as any call into managed code may trigger a type load. There are 3 possible fixesWhen running tests the following assertion appeared
From looking at the dump, the callstack apppears as
Configuration
This appeared while running standard PR tests on a Windows X86 Checked leg.
The text was updated successfully, but these errors were encountered: