-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fatal error. Internal CLR error. (0x80131506) #65890
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. |
Tagging subscribers to this area: @dotnet/gc Issue DetailsConfiguration:
|
Stacktrace:
|
@VSadov more x86 thread suspension issues. |
Hmm. Windows7. It could be something now or could be a regression caused by the workaround for Win11. |
The redirect context is NULL. It is supposed to be preallocated before redirecting a thread. Perhaps there is some kind of OOM condition involved. After a recent change for GC stress the first use of the context is Should just check |
#65910 should fix the issue |
"Fix" in the sense that it could be a preexisting problem that sometimes we cannot allocate or initialize the context. It is still not clear why allocation fails. It could happen in a case of memory shortage, but frequency seems a bit too high for that. So - it looks like we have exposed a preexisting issue and there is a fix for that. |
Also - is this Windows7/x86 only? I do not think I have seen reports with other combinations and cannot repro the issue on my machines (they are not Win7) |
Configuration:
net7.0-windows-Release-x86-CoreCLR_release-Windows.7.Amd64.Open
Build
Console log
The text was updated successfully, but these errors were encountered: