[vbox-dev] possible cause for the crash when shutting down a vm
huisinro at yahoo.com
Mon Jul 26 22:27:05 PDT 2010
more importantly, when WM_VBOX_RENDERSPU_DESTROY_WINDOW is received, should the while loop break out? that loop will definitely causes problems after dll is unloaded.
--- On Mon, 7/26/10, Huihong Luo <huisinro at yahoo.com> wrote:
From: Huihong Luo <huisinro at yahoo.com>
Subject: [vbox-dev] possible cause for the crash when shutting down a vm
To: vbox-dev at virtualbox.org
Date: Monday, July 26, 2010, 10:04 PM
I continue to debug the crash bug when shutting down a vm on windows host.
The crash indicated that some code is still being executed after a dll is unloaded.
After some extensive debugging, I found the following function might be problematic. Can you guys double check?
When WM_VBOX_RENDERSPU_DESTROY_WINDOW is received, it immediately invokes SetEvent(render_spu.hWinThreadReadyEvent), should that statement be commented out? and leave the last one.
static DWORD WINAPI renderSPUWindowThreadProc(void* unused)
else if (msg.message == WM_VBOX_RENDERSPU_DESTROY_WINDOW)
CRASSERT(msg.lParam && !msg.wParam);
render_spu.dwWinThreadId = 0;
crDebug("RenderSPU: Window thread stopped (%x)", crThreadID());
-----Inline Attachment Follows-----
vbox-dev mailing list
vbox-dev at virtualbox.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vbox-dev