http://bugs.winehq.org/show_bug.cgi?id=31442
--- Comment #17 from voidcastr voidcastr@gmail.com 2012-10-01 12:35:48 CDT --- Henri, I added you to the CC list because -- if my git skills don't fail me -- you appear to be one of the authors of the code that *might* be related to the problem discussed here.
---
I identified the origin of the message (as obtained from the log in my previous post) "fixme:d3d:wined3d_occlusion_query_ops_get_data 0x398c9598 Wrong thread, returning 1." as dlls/wined3d/query.c, method static HRESULT wined3d_occlusion_query_ops_get_data(struct wined3d_query *query, void *pData, DWORD dwSize, DWORD flags)
Since the -dx9single flag is suspected to disable multithreaded rendering and the above message (which is only shown when omitting the flag) complains about erroneous threading circumstances, I suspect it to be somewhat related to the freeze crash.
Nevertheless, I don't even know if this fixme is even to be considered critical. I'm really grapsing at straws here since I cannot find a suitable debug channel yielding ANY usable output in the moment the game freezes.
So... I'm open for any suggestions.