http://bugs.winehq.org/show_bug.cgi?id=13335
--- Comment #37 from Tony Wasserka tony.wasserka@freenet.de 2008-05-26 11:03:00 --- Reverting 220163ee9d698543fe34257969a88e5976d378de also fixed the problem for me. The errors still occur but it doesn't seem to affect the performance, thank you so much :D However, perhaps someone could try the minimize the code in the now re-added function in order to find the problematic code.
Ok, I guess I have hijacked this bug for a different one. (Both with ATI, slow rendering, and introduced about at the same version.)
Shall I open a new bug report to discuss my problem further? Overall, it is a regression that needs to be fixed, even if the code removal that triggered the bug was correct.
No, that isn't valid. You can't call a bug "reproducable" if it needs a patch to occur. Better wait for anyone to fix this one issue and try it again. Probably just some code that was re-added now conflicts with the newer code.