http://bugs.winehq.org/show_bug.cgi?id=25484
--- Comment #9 from Patrick Stokman patrick_stokman@hotmail.com 2010-12-12 16:31:03 CST --- I was too quick to say that 1.2.1 does not have this problem, as it just occurred again. I haven't done the regression testing yet, but it seems that the problem was always there, but recent builds made it happen faster/more frequent. I haven't found the exact circumstances yet to trigger this bug.
I know this won't help you much with the debugging, but I have been thinking and I remembered that it happened on occasion with 1.0 and pre-1.0 builds. If the 'faulty' code can be found between 1.3.2 and 1.3.3 as noted in the bug report I linked to (#25040), you will probably get a lot closer to the fix. I hope.