http://bugs.winehq.org/show_bug.cgi?id=4166
arieldembling@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|deadlock in GlobalUnlock |deadlock in GlobalUnlock | |(heap corruption?)
------- Additional Comments From arieldembling@gmail.com 2006-05-01 23:43 ------- OK, I've talked with Vitaliy some more, and we think this could be caused by heap corruption.
The application hangs in a loop calling GlobalUnlock repeatedly and waiting for it to return FALSE (binary 0) which would mean that the object whose handle is 7ff2d842 is unlocked. Sadly, this never happens, so GlobalUnlock always returns TRUE (binary nonzero), meaning that the object is still locked.
Now, why is the object never unlocked??? That's what I'll try to see by tracing +heap. I'll report the findings here.