Skip to content
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

Unit test deadlock during xUnit Shutdown #40369

Closed
jasonmalinowski opened this issue Dec 13, 2019 · 4 comments · Fixed by #49355
Closed

Unit test deadlock during xUnit Shutdown #40369

jasonmalinowski opened this issue Dec 13, 2019 · 4 comments · Fixed by #49355
Assignees
Labels
Area-Infrastructure Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented

Comments

@jasonmalinowski
Copy link
Member

This was hit in a CI run. The unit test shutdown of the AppDomain hung here:

 	clr.dll!MsgWaitHelper(int numWaiters, void * * phEvent, int bWaitAll, unsigned long millis, int bAlertable) Line 4258	C++
 	[Inline Frame] clr.dll!Thread::DoAppropriateAptStateWait(int) Line 4323	C++
 	clr.dll!Thread::DoAppropriateWaitWorker(int countHandles, void * * handles, int waitAll, unsigned long millis, WaitMode mode) Line 4468	C++
 	clr.dll!Thread::DoAppropriateWait(int countHandles, void * * handles, int waitAll, unsigned long millis, WaitMode mode, PendingSync * syncState) Line 4135	C++
 	[Inline Frame] clr.dll!SOIntolerantTransitionHandler::SetNoException() Line 853	C++
 	clr.dll!CLREventBase::WaitEx(unsigned long dwMilliseconds, WaitMode mode, PendingSync * syncState) Line 849	C++
 	clr.dll!AppDomain::UnloadWait(ADID Id, ADUnloadSink * pSink) Line 11187	C++
 	clr.dll!AppDomain::UnloadById(ADID dwId, int fSync, int) Line 11166	C++
 	clr.dll!AppDomainNative::Unload(int dwId) Line 1235	C++
@jasonmalinowski
Copy link
Member Author

Failed run was here. Dump has been copied to \\mlangfs1\public\jasonmal\Dumps\Roslyn\40369.

@sharwell
Copy link
Member

I hit this today as well. Looks like it's blocked in COM code.

@jasonmalinowski
Copy link
Member Author

Yeah, it's blocked in some COM wait, but I had no idea what it was doing.

@JoeRobich
Copy link
Member

Hit this again in Attempt #1

@sharwell sharwell self-assigned this Nov 13, 2020
@sharwell sharwell added the Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented label Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure Resolution-Fixed The bug has been fixed and/or the requested behavior has been implemented
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants