http://bugs.winehq.org/show_bug.cgi?id=17955
--- Comment #48 from Marc-Olivier Barre marco@marcochapeau.org 2009-08-26 08:17:35 --- (In reply to comment #47)
Since commit batch dated 20, 21 or 24 aug i do not get these crashes anymore - i.e. issue seems to be fixed in current git.
Let's wait .29 and get final confirm from other users to close this...
Ok, I see I'm going to need to spell it out.
For most easily reproducible bugs one can just "wait" for a magical fix to appear out of nowhere. Because of it's reproducible nature, it's easy to test if the bug is gone or not, and eventually trace down which commit fixed it (thus getting the knowledge of what to do if it "magically" reappears...)
Here, we are facing a Random Bug (TM). One of those which trigger is not obvious/straight-forward (like "clicking somewhere"). Some people - including me - have reported that under some circumstances, the bug was not reproducible until several hours had passed (I pushed that to over 12).
This means, unless we get a clean explanation, reason of failure and patch for this, we will never know if it was really fixed for sure.
This takes us back to issue number one : could a wine dev please help us track this down ?