Emulator Issues #7384
Crash in GCPad Configuration dialog
What's the problem? Describe what went wrong in few words.
When a keybinding button on the dialog is clicked 3 times and then the button on the controller is pressed, Dolphin crashes with an
....\src\common\evtloopcmn.cpp(110): assert "Assert failure" failed in wxEventLoopBase::Yield(): wxYield called recursively
error in WxWidgets.
What did you expect to happen instead?
The same effect as pressing the button once: the button should become bound.
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
1. Open the GCPad window with a controller attached and selected
2. Click on the binding button for "D-Pad: right" three times
3. Press any button on the attached controller
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
Which versions of Dolphin did you test on?
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
Did not test.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Windows 8.1 (64-bit, with Update 1 installed), Intel(R) Core(TM) i5-4210Y CPU @ 1.50GHz, Intel HD Graphics (integrated), Logitech Cordless RumblePad 2
Are you using the 32 or the 64 bit version of Dolphin?
Is there any other relevant information? (e.g. logs, screenshots,
[Upload big files to a hosting service and post links here!]
(I could not find a symbols file for Dolphin: if you can provide one, I can do a backtrace in WinDbg if that would be helpful)
[Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images and pastie.org for logs.]
#2 Updated by zhuoweizhang almost 6 years ago
here's a stack trace if that helps: I compiled the latest code off master.
#3 Updated by MayImilae almost 6 years ago
- Status changed from New to Accepted
- Priority set to Low
- Category set to ui
Confirmed, but there are some problems with the report. First of all, Dolphin does not -crash-. It brings up a wx warning. Hitting cancel on the warning will allow Dolphin to continue, and it will stop fussing about it from then on.
Pressing it 5 times then pressing a button, now THAT crashes Dolphin. Unless you already did the pressing 3 times thing above and hit cancel, which for some reasons means it will work, albeit slowly. Stupid WX.
Reproduced in 4.0 and 3.5.