http://bugs.winehq.org/show_bug.cgi?id=18636
--- Comment #11 from 3vi1 winehq.org@eternaldusk.com 2009-08-10 08:40:21 --- If it's due to the drivers, then it's unfortunately still occurring with 190.18.03, as per my dupe noted above (Bug 19621).
Testing with TF2, I find I do see the same blocking behavior (hung hl2.exe) on Steam as noted here. Oddly, hl2.exe terminates when testing with CS:S.
I did a debug and didn't see anything that's not already in Vitaliy's log above. They culminate in pretty much the same way:
... trace:d3d:context_clean_fbo_attachments glFramebufferTexture2D() call ok ../../../wine.git/dlls/wined3d/context.c / 97 trace:d3d:context_clean_fbo_attachments glFramebufferTexture2D() call ok ../../../wine.git/dlls/wined3d/context.c / 100 wine: Unhandled page fault on read access to 0x00000004 at address 0x7d3fda38 (thread 0044), starting debugger... Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x7d3fda38).
CS:S seems to be doing pretty much the same thing before it dies:
... trace:d3d:context_clean_fbo_attachments glFramebufferTexture2D() call ok context.c / 97 trace:d3d:context_clean_fbo_attachments glFramebufferTexture2D() call ok context.c / 100 wine: Unhandled page fault on read access to 0x00000004 at address 0x7d24b5f8 (thread 0051), starting debugger... err:ntdll:RtlpWaitForCriticalSection section 0xc074fc "?" wait timed out in thread 001f, blocked by 0020, retrying (60 sec) Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x7d24b5f8).