-
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
Test failure baseservices/threading/regressions/2164/foreground-shutdown/foreground-shutdown.cmd #84006
Comments
Tagging subscribers to this area: @mangod9 Issue DetailsRun: runtime-coreclr gcstress-extra 20230326.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr gcstress-extra 20230402.1 Failed test:
Error message:
|
@kouvel could you please take a look? |
Failed again in: runtime-coreclr gcstress-extra 20230409.1 Failed test:
Error message:
|
Ping @kouvel |
Failed again in: runtime-coreclr gcstress-extra 20230416.1 Failed test:
Error message:
|
Failed again in: runtime-coreclr gcstress0x3-gcstress0xc 20230507.1 Failed tests:
Error message:
Stack trace:
|
This test has failed across many configurations, but apparently only on Windows. Tracked by dotnet#84006, dotnet#83658.
Moving to 9 since this is disabled. |
…pending on timing with GCs - On Windows when a thread calls `ExitProcess`, the `TlsDestructionMonitor` for the thread appears to be destructed after all other threads in the process are torn down. It's possible for a GC to be in progress during that time, and the thread cleanup code in `TlsDestructionMonitor` tries to enter cooperative GC mode to fix the frame pointer, leading to a hang. Fixed by deactivating the `TlsDestructionMonitor` for the thread before calling `ExitProcess`. - Also disabled the relevant test due to a different issue dotnet#83658 occurring in the same test on multiple platforms/architectures that is not understood yet. Fixes dotnet#84006
From what I can see this is no longer disabled. |
It looks like it's still disabled here: runtime/src/tests/issues.targets Lines 30 to 32 in 3eba702
|
Run: runtime-coreclr gcstress-extra 20230326.1
Failed test:
Error message:
The text was updated successfully, but these errors were encountered: