Emulator Issues #7737
closed
Pressing Shift Causes Emulator to Crash
0%
Description
Game Name?
ANY
(Tested with LoZ: Wind Waker & Baten Kaitos Origins (both US))
Game ID?
ANY
(Tested with GZLE01 & GK4E01)
What's the problem? Describe what went wrong in few words.
Pressing SHIFT at any time causes the emulator to crash.
Emulator will continue to run for some odd reason.
Pressing any other key after that will white-screen the window
(Windows's way to say the window isn't responding).
What did you expect to happen instead?
Would like to press SHIFT-F1 to save game states.
Utilizing menus saves states normally, but would rather use shortcuts.
What steps will reproduce the problem?
- Press Shift (left is what I use).
Which versions of Dolphin did you test on?
4.0-3557
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Cannot recall exactly, but 4.0-2xxx.
What are your PC specifications?
http://speccy.piriform.com/results/ZLcPwanL7VtDRRmJSDaT4Fd
Intel Core i5 2500k @ 3.3GHz (quad-core)
GeForce GTX 750 2GB
Windows 8.1 Pro with Media Center
8GB DDR3 RAM
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
No.
Updated by rjsec4ever over 9 years ago
As I'm beginning to recall which version was last stable for this, I know for a fact that it was fine around 3 July 2014. It was the latest build at that time that was the version I updated from.
Updated by rjsec4ever over 9 years ago
ACTUALLY... I want to confirm that it's EVERY key on the keyboard: tried loading 1st slot savestate, pressing F11, even using a directional key... all caused Dolphin to crash. My input method is the 360 controller, however. All bindings to Gamecube controllers via keyboard has been removed.
Updated by rjsec4ever over 9 years ago
Video showing issue: http://youtu.be/2tP-46TQ_Lg
Updated by JMC4789 over 9 years ago
That just shows me your computer is having problems (likely with WXWidgets?) but it doesn't help me with reproducing, unfortunately. When it crashes, open up task manager/processor before closing it and right click dolphin.exe and Dump the core file or whatever it says on the list.
That would help, I think.
Updated by rjsec4ever over 9 years ago
Alright. Dumped the file right after said crash, but it is a 906 MB file.
Only best place for me to upload the file is to MediaFire, but with a 5/1 DSL connection, it will take some time.
Updated by rjsec4ever over 9 years ago
Dolphin.7z >> Dolphin.DMP
https://www.mediafire.com/?51anim3kcckzwlt
MD5: F2CB30894BCDBDCFBDAD7117F21566DD
Updated by Anonymous over 9 years ago
The crash dump shows the wxw thread is currently in this loop:
https://github.com/dolphin-emu/dolphin/blob/master/Source/Core/DolphinWX/Frame.cpp#L1102
Probably we are doing something wrong which causes the same event to be sent over and over (or similar)...
Updated by JMC4789 over 9 years ago
Can anyone fix this? Is it a bug on our end?
Updated by rjsec4ever over 9 years ago
4.0-3730 is fine, as far as I know. Only have to report a bug involving getting out of exclusive fullscreen... which I hardly use anyway.
Updated by Stevoisiak over 9 years ago
- Status changed from Questionable to Fixed
User has stated issue was fixed.