http://bugs.winehq.org/show_bug.cgi?id=31442
--- Comment #36 from Henri Verbeet hverbeet@gmail.com 2012-10-07 09:30:27 CDT --- (In reply to comment #34)
The most suspicious thing I see is a call to "user32.SendMessageW(...)" by TID 0044 apparently never returning... at least this could explain the many "KERNEL32.WaitForSingleObjectEx()" messages repeated over and over again by TID 002f, which might just be waiting for 0044. Btw, throughout the entire log (not just the excerpt), there is only one other call of TID 0044 to "user32.SendMessageW(...)" and that one's immediately returning (it can be seen at the end of the 3rd block in the attachment).
The 0x281 is WM_IME_SETCONTEXT. If that's really related, WINEDEBUG=+imm may be of interest, perhaps with some additional traces added to dlls/imm32/ to see where exactly it hangs. It's also possible that the window 0x80064 belongs to a different thread that isn't processing messages for some reason, e.g. because it's waiting for something itself.