http://bugs.winehq.org/show_bug.cgi?id=31442
--- Comment #29 from voidcastr voidcastr@gmail.com 2012-10-03 05:24:01 CDT --- The latter point led me to the assumption that the thread is indeed NOT crashing but just waiting forever while not even failing after a timeout. This might be the case because there simply IS no finite timeout. This, in turn, might be related to calls to
NTDLL_wait_for_multiple_objects or NtWaitForMultipleObjects
with timeout=(nil), which can be observed in the backtrace in comment #25
Though, this is just a guess. I don't know the semantics of the above functions' parameters and whether or not passing a nil timeout to them is discouraged, i.e. might cause lock situations.