http://bugs.winehq.org/show_bug.cgi?id=19217
--- Comment #6 from Steve McKnelly denali@shadowforge.net 2009-07-09 10:25:05 --- (In reply to comment #5)
I doubt that commit makes any difference. If it did, it would appear as a fixme in the backtrace, This looks a lot more likely: err:threadpool:iocp_poller NtRemoveIoCompletion failed: 0xc0000008 You should have seen an unhandled exception in unimplemented function GdipIsVisibleRegionPointI long before now if that is indeed the cause. What happens if you revert that commit? Also, attach this bug to the correct version of EVE, I have to do this every time an EVE bug is opened!
RE: Add to EVE in AppDB - Done
RE: Commit itself - Honestly, I was pretty surprised myself. There were other commits that I was actually betting on that were removed by bisect. When I got down to two commits left, the one that didn't have this commit worked fine, if I read git bisect visualize correctly.
I will revert this patch on my local repository tonight to see what happens. The glitch is trivial to cause. You simply open several windows in the game including one with a list and scroll the list up and down repeatedly. After about 3-4 minutes, the windows in the game will start flashing. After 5-6 minutes, you start to see the graphic corruption shown in the JPG I attached. After 7-10 minutes, the game crashes but won't complete debug.