https://bugs.winehq.org/show_bug.cgi?id=49532
Paul Gofman pgofman@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |pgofman@codeweavers.com
--- Comment #17 from Paul Gofman pgofman@codeweavers.com --- Created attachment 68138 --> https://bugs.winehq.org/attachment.cgi?id=68138 Add SIGQUIT to server block set
I've tested the issue and that was happening in a random way for me. With default output it was hard to reproduce and much easier with certain logging added.
It looks like some .net processes hang on termination. All of the threads are doing normal shutdown when on of them calls ExitProcess. Some of the remaining threads receive SIGQUIT from wineserver while holding virtual_mutex (freeing VM from virtual_free_teb) and get force terminated without unlocking it. Meanwhile the thread which called NtTerminateProcess is spared from getting SIGQUIT, and locks forever on NtUnmapViewOfSection on virtual mutex.
The attached patch seems to fix the issue for me, at least I was not able reproduce the hang after several attempts.