http://bugs.winehq.org/show_bug.cgi?id=27848
--- Comment #5 from rocko rockorequin@hotmail.com 2011-07-25 00:29:43 CDT --- The bad commit might be be here or nearby:
26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 is the first bad commit commit 26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 Author: Henri Verbeet hverbeet@codeweavers.com Date: Thu Jun 16 00:40:32 2011 +0200
wined3d: Check the correct debug class in checkGLcall.
:040000 040000 6a22b35e6d518f2e5c42d6cdeedc2ba41bcd9094 2da11cafd991229dc13ccfb8a01740a5d4eafead M dlls
It's hard to be completely sure because while bisecting I found with commits near to that commit the game freezes but there is also an nvidia crash relating to interrupts that brings down the entire kernel and so this might be the cause of the freeze. eg this happened when I compiled wine up to and including commits 26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 and e532c55995989f9ad4625e876fe93b71d6b476f1.
I know for sure that when I compiled up to commit ffb8f4bedf709dd63f6f9ec1569dc99873021a11 (rpcrt4: Add support for float parameters in client calls on x86_64) I have experienced the non-nvidia wine freeze, ie this bug.
Running with wine compiled up to 46215689221aa820b94d2ce288613d6e0b373f77 (wined3d: Only invert viewport y for onscreen destinations in surface_depth_b) so far seems good. I'll report back if I manage to crash it.