https://bugs.winehq.org/show_bug.cgi?id=51479 François Gouget <fgouget(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from François Gouget <fgouget(a)codeweavers.com> --- Adding some details from my duplicate bug report... As far as I can tell this issue is not caused by a specific process so a simple way to reproduce it is to run something like: $ ./wine hostname.exe /? INTEL-MESA: warning: Haswell Vulkan support is incomplete Usage : hostname $ wine: Unhandled page fault on write access to 00000000 at address 7E95C4D1 (thread 0070), starting debugger... 0070:err:seh:start_debugger Couldn't start debugger L"winedbg --auto 96 64" (1115) Read the Wine Developers Guide on how to set up winedbg or another debugger winedbg.exe is not really usable because it prevents Wine from shutting down and winedevice.exe from exiting. But tracing showed that the crash happens in the libusb_close() call of fdo_pnp() in dlls/wineusb.sys/wineusb.c: https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/wineusb.sys/wineusb.c... This is with Debian's version 2:1.0.22-2 of the libusb-1.0-0 and libusb-1.0-0-dev packages. All I found online is that libusb_close() typically crashes when there are control transfers still in progress. So maybe this is a cleanup issue? Since this started with b065daa600 which changed the shutdown procedure, maybe this is related to the cleanup issue mentioned above. -- 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.