-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
GC/Scenarios/DoublinkList/doublinkgen fails occasionally in CI #6435
Comments
@swgillespie Can you take a look at this please? |
Seems the same as https://github.com/dotnet/coreclr/issues/4093 . This one hasn't shown up in a while, but it looks to be the same as when I observed it a few months ago. It's not obvious what's happening here. I've been unable to repro this locally and it does only seem to repro on checked Ubuntu builds. Now that it's showing up again I'll see if I can get a repro. |
Added another failure to the list above. |
Another, this time with an abort:
|
@stephentoub got a crash dump from that, thanks! |
Here's another instance in case you need it: https://ci.dot.net/job/dotnet_coreclr/job/master/job/checked_ubuntu_flow_prtest/238/ |
Yet another instance: |
thanks! |
So, what all of these dumps have in common is that, after the second induced GC after In Stephen's dump:
Jan's dump:
I'm trying to think of a feasible sequence of events that can result in things remaining in the finalizer queue after |
Here's another instance: https://ci.dot.net/job/dotnet_coreclr/job/master/job/checked_ubuntu_flow_prtest/1438/consoleText |
* Disable DoublinkGen (see #6574) * Add test to testsFailingOutsideWindows.txt
Closing in favor of #5496, which tracks this particular issue. |
Example output:
Examples of failing jobs:
http://dotnet-ci.cloudapp.net/job/dotnet_coreclr/job/master/job/checked_ubuntu_tst_prtest/3728/
http://dotnet-ci.cloudapp.net/job/dotnet_coreclr/job/master/job/checked_ubuntu_tst_prtest/3747/
http://dotnet-ci.cloudapp.net/job/dotnet_coreclr/job/master/job/checked_ubuntu_tst_prtest/3768/
The text was updated successfully, but these errors were encountered: