http://bugs.winehq.org/show_bug.cgi?id=32524
Bug #: 32524 Summary: mmdevdrv assertion failure on FarCry3 loading screen Product: Wine Version: 1.5.18 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: kug3lblitz@gmail.com Classification: Unclassified
When playing FarCry 3, my wine crashes with the following assertion failure:
xe: mmdevdrv.c:534: pulse_wr_callback: Assertion `oldpad >= This->pad' failed. wine: Assertion failed at address 0xf7753425 (thread 0039), starting debugger...
So far, this has happened every time at the same loading screen (3/3) but not on other loading screens. The loading screen in question is the first one in the middle of the mission to pirate cove.
http://bugs.winehq.org/show_bug.cgi?id=32524
--- Comment #1 from Nikolay Sivov bunglehead@gmail.com 2012-12-23 07:45:14 CST --- Are you using winepulse by any chance? I don't see this function in wine tree. If so it's an unsupported configuration.
http://bugs.winehq.org/show_bug.cgi?id=32524
--- Comment #2 from Mirko kug3lblitz@gmail.com 2012-12-23 10:45:20 CST --- You are correct, I was using wine from an Ubuntu PPA which was using winepulse.
I tried the same with a vanilla wine 1.5.17 compiled some time ago from git. The game crashes at the same spot, though this time without the assertion of course. The error reads:
wine: Unhandled page fault on write access to 0x00000000 at address 0x78aa1ed7 (thread 0045), starting debugger...
I tried running the game with the latest wine from git, but I cannot get it to start. It seems like the game tries to use DX11 with the latest wine which is not fully implemented yet.
wine: Call from 0x7b83b452 to unimplemented function d3d11.dll.D3D11CreateDevice, aborting
Is there a way I can force the game to use DX9? There is a dedicated executable for DX11 but none for DX9, so I guess there is some auto detection going on by the game.
http://bugs.winehq.org/show_bug.cgi?id=32524
--- Comment #3 from Nikolay Sivov bunglehead@gmail.com 2012-12-23 11:00:02 CST --- (In reply to comment #2)
Yes, it's not implemented at all.
Some users report it works if you disable d3d11 in winecfg.
http://bugs.winehq.org/show_bug.cgi?id=32524
--- Comment #4 from Mirko kug3lblitz@gmail.com 2012-12-23 11:45:20 CST --- (In reply to comment #3)
Some users report it works if you disable d3d11 in winecfg.
Thank you, this indeed makes it possible to run the game with the latest wine from git. Might I ask where you got this information from? I could find no mention of it in the AppDB when I looked there myself.
Sadly, the game still crashes at the same spot, now with another message however. I get a lot of these right before the game crashes:
mmap() failed: Cannot allocate memory
I don't think I ran out of memory (I have 8GB) so I guess there is some other issue that is causing this crash.
https://bugs.winehq.org/show_bug.cgi?id=32524
--- Comment #5 from Austin English austinenglish@gmail.com --- Is this still an issue in current (1.7.35 or newer) wine? If so, please attach terminal output.
https://bugs.winehq.org/show_bug.cgi?id=32524
Mirko kug3lblitz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #6 from Mirko kug3lblitz@gmail.com --- (In reply to Austin English from comment #5)
I can no longer reproduce the problem with the newest wine from git, so it seems the issue is resolved.
Thanks to the unknown developer who fixed this issue :)
https://bugs.winehq.org/show_bug.cgi?id=32524
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.36.