https://bugs.winehq.org/show_bug.cgi?id=54115 Bernhard Übelacker <bernhardu(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernhardu(a)mailbox.org --- Comment #9 from Bernhard Übelacker <bernhardu(a)mailbox.org> --- Created attachment 74577 --> https://bugs.winehq.org/attachment.cgi?id=74577 backtrace of crash and fprintf in winedevice.exe I received this message too. My environment is a regular 64+32-bit mingw build. Inside a fresh prefix created with just WINEARCH=win32. And running on top of a current Debian testing. Starting just notepad or winecfg and a few seconds after closing it, probably when wineserver terminates it shows the message. wine client error:e0: write: Bad file descriptor When temporarily starting winedbg before closing notepad, the thread id from the message belongs to rpcss.exe. When running inside rr-debugger it belongs to a winedevice.exe. This might be a race when shutting down processes with multiple threads. In my example I saw they do execute signal_exit_thread, two receive a SIGQUIT signal. Then thread 1 executes signal_exit_thread but crashes. Unfortunately handling this crash executes a NtCreateEvent, which needs a wineserver roundtrip, which seems no longer available at this time, therefore this message is written. Attached are the backtrace of the crash and fprintf in winedevice.exe. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.