On one of my boxes, if I run winmm/midi.ok in a loop, it will eventually deadlock/crash ( http://bugs.winehq.org/show_bug.cgi?id=28388 ): err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 0022, blocked by 001f, retrying (60 sec) wine: Critical section 00110060 wait failed at address 0x7bc3484a (thread 0022), starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 0022, blocked by 001f, retrying (60 sec)
Sadly, no backtrace follows ( http://bugs.winehq.org/show_bug.cgi?id=28265 ). Since I'm not around when it finally happens, I haven't tried btall yet.
I suppose I should write a shell script to watch for that error message in the log, and run btall then... any better ideas?
(I did try giving winedbg a private heap, didn't seem to prevent the deadlock.)
Hey Dan,
On 09/29/2011 06:00 AM, Dan Kegel wrote:
On one of my boxes, if I run winmm/midi.ok in a loop, it will eventually deadlock/crash ( http://bugs.winehq.org/show_bug.cgi?id=28388 ): err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 0022, blocked by 001f, retrying (60 sec) wine: Critical section 00110060 wait failed at address 0x7bc3484a (thread 0022), starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main process heap section" wait timed out in thread 0022, blocked by 001f, retrying (60 sec)
Sadly, no backtrace follows ( http://bugs.winehq.org/show_bug.cgi?id=28265 ). Since I'm not around when it finally happens, I haven't tried btall yet.
I suppose I should write a shell script to watch for that error message in the log, and run btall then... any better ideas?
(I did try giving winedbg a private heap, didn't seem to prevent the deadlock.)
I'm wondering if it's because of the lock in virtual_handle_stack_fault, what if you remove that? :P
On Fri, Sep 30, 2011 at 1:29 AM, Maarten Lankhorst m.b.lankhorst@gmail.com wrote:
On 09/29/2011 06:00 AM, Dan Kegel wrote:
On one of my boxes, if I run winmm/midi.ok in a loop, it will eventually deadlock/crash ( http://bugs.winehq.org/show_bug.cgi?id=28388 ):
I'm wondering if it's because of the lock in virtual_handle_stack_fault, what if you remove that? :P
I did write a nice script to do a btall automatically when the lockup happens.
With git, on my e8400, with WINEDEBUG=warn+heap, I get roughly 4 lockups per 100 runs.
Under the same conditions, but without the lock in virtual_handle_stack_fault, I get ... roughly 4 lockups per 100 runs.
And the stacks look the same.
-
Dan Kegel -
Maarten Lankhorst