-
Notifications
You must be signed in to change notification settings - Fork 1k
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
ErrorProviderAccessibleObjectTests.Ctor tests flakey #3391
Comments
Yes, just saw it too. I haven't seen it before... 😕 |
That looks like an actual bug and not just misbehaving tests
There is a static weak reference list in play here, so this test interacts with all other tests ever having entered something in that list. Normally this is supposed to be designed threadsafe & cleanup correctly in response to GC/Disposal. Looking at the implementation I cannot see any threadsafety logic like locks, so maybe this is just a race condition triggered in the middle of cleanup when having multiple UI threads and some other thread tries to clean up its DC at the same time someone adds his DC? Either that or there is a more general cleanup logic bug where someone forgets to clean up his DC entirely. I'd suggest starting by figuring out what the proper scope for adding thread safety is (unless its already threadsafe and I missed the scope at which locks are taken) |
Randomly happened to me locally as well, not limited to CI, but seems to be quite rare to trigger (at least for me) so I couldn't catch it under a debugger yet. I still think the above explanation of not being threadsafe makes most sense of what could be the cause. While investigating I also found |
#3441 should have a dump in the 2nd failed test run, maybe could try using it to confirm the multithreading issue, but probably not necessary |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Another one: https://dev.azure.com/dnceng/public/_build/results?buildId=732876&view=artifacts&type=publishedArtifacts @JeremyKuhne do you think it can be solved in conjunction with you work? |
#3553 should take care of this |
Yes the PR removes the problematic
|
.NET Core Version:
Master
Have you experienced this same bug with .NET Framework?:
N/A
Problem description:
In #3366
The text was updated successfully, but these errors were encountered: