Emulator Issues #6655
closed
Dolphin crash after selecting another interface theme
Added by JohnGrigius over 11 years ago.
Updated about 7 years ago.
Status:
Working as intended
Relates to performance:
No
Relates to maintainability:
No
Description
What went wrong?
After selecting another interface theme in the Config settings and clicking OK, a popup comes up saying that Dolphin is not working anymore and needs to be shut down. The new chosen theme however saves the second time you start up Dolphin.
What did you expect to happen instead?
Not crashing
What steps will reproduce the problem?
[Don't assume we have played the game and know its level names. Be as
detailed as possible.]
1.Go to the Config settings, select the tab Interface settings
2.Choose another theme than the one you're using
3.Click OK
Which versions of Dolphin did you test on?
Dolphin 4.0
Which version of Dolphin used to work?
Dolphin 3.5
What are your PC specifications (example: Operating System, CPU and GPU)?
Windows 8 64-bit with Dolphin 4.0 64bit
i5 3570K at 3.4Ghz (not OC'ed)
GTX 660Ti
8 GB RAM and 1TB HDD
- Status changed from New to Accepted
- Category set to ui
I kind of found a way to reproduce this crash:
- Start Dolphin 4.0 and select DX 9 or DX 11 as the backend, close the dialog.
- Close Dolphin completely
- Start Dolphin again and then immediately click the Graphics settings icon, don't do anything else before that.
- DON'T CHANGE ANYTHING in the settings and close it
- Now click the Config settings icon, go to the interface settings tab and change the interface theme (doesn't matter which one), click OK
Only this way produces the crash for me. This doesn't occur on Windows 7 (32bit) though.
It does happen on win 7 too.
Tagging comex, since he made some recent WX changes and might be able to help.
Would this only be fixed in the next Git build or would Dolphin 4.0 be fixed as well?
This has been known for a very long time now, i wouldn't expect it to be fixed any time soon, because no one cares about it.
Nothing will be fixed in 4.0 though. That's the entire point of stable releases: they don't change.
I'm surprised I never heard of this bug while it's known for such a long time. Googling it also doesn't find anything.
Not to be rude or anything but I guess the entire point of stable releases is Dolphin being stable as well, right? I read on the home page that 4.0.1 will be released soon fixing another bug. Oh well, hopefully someone will care about this one soon enough...
Not seeing this on Windows 10, anyone on Windows 7 able to test is this is still an issue?
- Status changed from Accepted to Working as intended
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by