[GD-Windows] Process hanging inside ExitProcess()
Brought to you by:
vexxed72
From: Javier A. <ja...@py...> - 2002-08-29 10:15:01
|
Hi! We currently have this annoying bug where, every few days, the game hangs when quitting, inside CRT's call to ExitProcess() with one (sometimes two) additional threads running. Of course, it only hangs in our retail builds, without our helpful debug logs. When we try to break into the debugger, it dumps the following message to the debug output: DBG: Break command failed within 3 seconds. DBG: Potential deadlock. Soft broken. The usual suspect is the multithreaded sound DLL, since the only reason ExitProcess() might hang seems to be while waiting for DLLs to detach. We use the undocumented MSVC++ 6 trick for assigning names to threads (cool!) so we can identify those in the debugger, but when we get this particular deadlock, MSVC++ seems to "forget" the names, and stack traces only show a couple levels inside KERNEL32, none of our user code. Thus we are not sure which DLLs and/or threads are causing this deadlock. Anybody has suggestions that can be helpful for debugging and/or solving this problem? Thanks in advance, Javier Arevalo Pyro Studios |