You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Crst ordering issue between threadpool and Process.EnableRaisingEvents under GCStress #38801
@kouvel@mangod9 - I came across this while triaging. Kount I think both the code versioning lock and the ThreadpoolWaitThreads lock fall in your area if you can untangle this lock inversion. At first glance it looked like the Process.EnableRaisingEvents part is a red hering and probably any workload that used threadpool in the right way could trigger this.
Activity
BruceForstall commentedon Jul 6, 2020
@sywhang @josalem
Disable reverseouter test under GCStress
Disable reverseouter test under GCStress (#39937)
josalem commentedon Jul 27, 2020
I can't seem to get this to reproduce locally with
COMPlus_gcstress=0xcandCOMPlus_TieredCompilation=0. I'll try with a few different gcstress modes.BruceForstall commentedon Jul 27, 2020
Note the failure above was
CoreCLR Windows_NT x86 Checked gcstress0xc @ Windows.10.Amd64.Open. It only seems to fail on x86.Here's the latest failure (from this weekend, before #39937):
https://dev.azure.com/dnceng/public/_build/results?buildId=746110&view=ms.vss-test-web.build-test-results-tab
josalem commentedon Jul 27, 2020
Looks like I got a repro under gcstress=0x3c, but not 0x3 or 0xc on their own.
Just now reading through the stack to see if I can pinpoint what happened.
17 remaining items
noahfalk commentedon Jul 21, 2022
@kouvel @mangod9 - I came across this while triaging. Kount I think both the code versioning lock and the ThreadpoolWaitThreads lock fall in your area if you can untangle this lock inversion. At first glance it looked like the Process.EnableRaisingEvents part is a red hering and probably any workload that used threadpool in the right way could trigger this.
kouvel commentedon Sep 20, 2022
This should be fixed now in main, the native thread pool has been removed
noahfalk commentedon Sep 21, 2022
Thanks Kount!