http://bugs.winehq.org/show_bug.cgi?id=30405
Bug #: 30405 Summary: WinUAE crashes on changing graphics API from DirectDraw to Direct3D Product: Wine Version: 1.5.1 Platform: x86-64 URL: http://www.winuae.net/files/InstallWinUAE2400.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: markk@clara.co.uk Classification: Unclassified
Created attachment 39746 --> http://bugs.winehq.org/attachment.cgi?id=39746 Backtrace output on crash
I'm testing with Wine 1.5.1, Lubuntu 11.10 64-bit, Nvidia driver 295.20.
This bug applies to version 2.4.0 of the WinUAE Amiga emulator. WinUAE can use either DirectDraw or Direct3D for its graphics output. I get a crash on changing the graphics API from DirectDraw to Direct3D after starting the emulation.
To reproduce the problem: - Download and run the WinUAE installer. Run WinUAE. - When the settings window appears, click Miscellaneous in the treeview. Note that the default graphics API is DirectDraw. - Click Start. The emulation window opens and after a few seconds the insert media screen appears. There's a red mouse pointer which you can move. - Press F12 to bring up the settings window. Click Miscellanous in the treeview and change Graphics API to Direct3D. - To work around Wine bug 10643, click in the emulation window then press and release F12. - Click OK to continue the emulation. - WinUAE usually crashes at this point. If it doesn't, repeat the previous three steps to change the graphics API again a few times.
In my testing, setting graphics API to Direct3D before starting the emulation, starting emulation then changing API to DirectDraw, I don't get a crash. The crash only seems to happen when switching from DirectDraw to Direct3D.
When it crashes, a dialog box appears with caption Crash, and text like this: Crash detected. MiniDump saved as: C:\Program Files\WinUAE\winuae_240_yyyymmdd_hhmmss.dmp On clicking OK a Wine Program Error window appears. Backtrace output from that is attached.
http://bugs.winehq.org/show_bug.cgi?id=30405
Mark K markk@clara.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, source CC| |markk@clara.co.uk
http://bugs.winehq.org/show_bug.cgi?id=30405
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |frederic.delanoy@gmail.com
--- Comment #1 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-04-10 09:23:19 CDT --- (In reply to comment #0)
Created attachment 39746 [details] Backtrace output on crash
Please repost the backtrace using a wine version with debugging symbols (generally named like "wine*-dbg")
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #2 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-04-10 09:26:12 CDT --- (In reply to comment #0)
Created attachment 39746 [details] Backtrace output on crash
I'm testing with Wine 1.5.1, Lubuntu 11.10 64-bit, Nvidia driver 295.20.
Also note 295.20 is buggy and you may want to try 295.33 first.
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #3 from Mark K markk@clara.co.uk 2012-11-04 07:48:53 CST --- I tested WinUAE 2.4.0 again using Wine 1.5.5 with the -dbg package installed, and wine-1.5.16-59-gdf2c73a which I built myself. On Lubuntu 11.10 x86-64, Nvidia driver 304.51.
Even with debugging symbols installed, no backtrace is shown when the program crashes. Can anyone else reproduce this problem?
http://bugs.winehq.org/show_bug.cgi?id=30405
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW CC| |00cpxxx@gmail.com Ever Confirmed|0 |1
--- Comment #4 from Bruno Jesus 00cpxxx@gmail.com 2012-11-04 18:38:44 CST --- I can confirm this issue in wine-git. Happened to me after the first graphic change. Unfortunately there is no backtrace and I don't know how to debug it better.
http://bugs.winehq.org/show_bug.cgi?id=30405
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #5 from joaopa jeremielapuree@yahoo.fr 2012-11-04 18:51:05 CST --- winedbg foo.exe could help
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #6 from Bruno Jesus 00cpxxx@gmail.com 2012-11-04 19:45:10 CST --- (In reply to comment #5)
winedbg foo.exe could help
Unfortunately it does not help:
Backtrace: =>0 0x00000283 (0x0000023e)
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #7 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-11-05 01:55:32 CST --- Created attachment 42394 --> http://bugs.winehq.org/attachment.cgi?id=42394 console output wine-1.5.16-160-gd89cd62
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #8 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-11-05 01:56:23 CST --- Tested with wine-1.5.16-160-gd89cd62. Could not get a really usable wine crash log, but a minidump was generated
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #9 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-11-05 01:57:36 CST --- Created attachment 42395 --> http://bugs.winehq.org/attachment.cgi?id=42395 minidump wine-1.5.16-160-gd89cd62
http://bugs.winehq.org/show_bug.cgi?id=30405
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #39746|0 |1 is obsolete| |
--- Comment #10 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-11-05 01:58:31 CST --- Created attachment 42396 --> http://bugs.winehq.org/attachment.cgi?id=42396 crash log wine-1.5.16-160-gd89cd62
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #11 from Frédéric Delanoy frederic.delanoy@gmail.com 2012-11-05 02:17:39 CST --- (In reply to comment #8)
Tested with wine-1.5.16-160-gd89cd62. Could not get a really usable wine crash log, but a minidump was generated
This extract from console log might be an explanation:
... fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. fixme:win:EnumDisplayDevicesW ((null),0,0x3fce208,0x00000000), stub! fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible.
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #12 from Henri Verbeet hverbeet@gmail.com 2012-11-05 04:13:58 CST --- (In reply to comment #11)
This extract from console log might be an explanation:
That shouldn't cause crashes, though "fixme:d3dx:d3dx9_base_effect_init HLSL ascii effects not supported, yet" might. You may want to give native d3dx9 / d3dcompiler a try. If that doesn't help, you'll probably want a "+seh,+tid,+ddraw,+d3d9,+d3d" log.
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #13 from Mark K markk@clara.co.uk 2012-11-05 05:59:54 CST --- (In reply to comment #11)
This extract from console log might be an explanation: ... fixme:d3d:swapchain_init The application requested more than one back buffer, this is not properly supported. ...
That's definitely not the cause of the crash. You can disable triple-buffering in WinUAE before starting the emulation: click Display in tree-view, change Triple buffering to Double buffering or No buffering. I still get the crash with it set to both No buffering and Double buffering.
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #14 from Mark K markk@clara.co.uk 2012-11-05 06:09:32 CST --- Created attachment 42399 --> http://bugs.winehq.org/attachment.cgi?id=42399 +seh,+tid,+ddraw,+d3d9,+d3d log for WinUAE 2.4.0 DD->D3D crash
(In reply to comment #12)
ascii effects not supported, yet" might. You may want to give native d3dx9 / d3dcompiler a try. If that doesn't help, you'll probably want a "+seh,+tid,+ddraw,+d3d9,+d3d" log.
I didn't try native anything, but here's a +seh,+tid,+ddraw,+d3d9,+d3d log in case it helps.
Created by: run WinUAE, select No buffering, start emulation, press F12, change to D3D click OK. No crash so F12 again, change to DirectDraw click OK. F12 change to D3D click OK. Crash.
http://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #15 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-05-24 06:48:59 CDT --- Still in wine-1.5.30-221-gedb01d2 (nVidia 313.26)
https://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #16 from Frédéric Delanoy frederic.delanoy@gmail.com --- Still in wine-1.9.18-121-g4e9cc30
https://bugs.winehq.org/show_bug.cgi?id=30405
--- Comment #17 from joaopa jeremielapuree@yahoo.fr --- Works fine with wine-5.0-rc3: switch directdraw->direct3D is OK. (you can test with the link http://www.winuae.net/download/ ) Can an administrator close this bu as FIXED?
https://bugs.winehq.org/show_bug.cgi?id=30405
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #18 from Jeff Zaroyko jeffz@jeffz.name --- Reported fixed.
https://bugs.winehq.org/show_bug.cgi?id=30405
Mark K mark_k@iname.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |---
--- Comment #19 from Mark K mark_k@iname.com --- I tested WinUAE 2.4.0 with Wine 5.0-rc3 and the problem is still present.
(joaopa probably tested with the latest version of WinUAE? That is much changed from 2.4.0.)
It looks like WinUAE 2.4.0 can be downloaded from https://osdn.net/projects/sfnet_winuae/downloads/WinUAE/2.4.0/WinUAE2400.zip...
https://bugs.winehq.org/show_bug.cgi?id=30405
Mark K mark_k@iname.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.winuae.net/files |https://osdn.net/projects/s |/InstallWinUAE2400.exe |fnet_winuae/downloads/WinUA | |E/2.4.0/WinUAE2400.zip/