-
-
Notifications
You must be signed in to change notification settings - Fork 782
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Program crashes when controller plugged in #3070
Comments
You're going to need to give me more information. Like, a lot more information. If this happened for everyone with every controller on every OS, you can be sure it'd have been fixed by now. |
Having the same issue here. Edit: I also tested with stuff like Steam not opened to make sure nothing external was messing around with the controllers of my computer, same results. I wanted to test the pro controller wireless but I failed to find my bluetooth dongle lol |
Sorry about the vague post. I believe my controller is this one: http://www.pc210.com/products/product_view.aspx?proid=430 |
Steps to reproduce:
The bug does not immediately appear, but rather requires (when reproducing in a games title screen) a variable amount (un-)plugs of the controller to occur (but sometimes a single (un-)plug is enough). And before somebody asks: No, I'm disconnecting my controller on purpose during the game, rather my controller is old and has a loose contact which results in short disconnects during the usage. Additional information:
Information about my setup / system: If this seems to be another issue, I'll create a new issue. But at the moment it looks like it could probably be the same issue. |
@spamzilla @Jaizu Was a game already running when mGBA crashed? If yes, it could probably prove my theory... I just took another look into it and threw gdb on it; I guess (in my case) the problem occurs through the invalidated reference when disconnecting the controller / the incompletely initialized reference when newly connecting a controller while the inputs are polled. At least thats's what I think could be the problem:
And even if my guess is incorrect, there's probably additional useful information about the bug. |
Pulling this into 0.10.3 since it seems more widespread than I'd originally expected. |
I am unable to reproduce a crash on 0.10.2, at least on Linux. I can, however, reproduce a crash on disconnect on master that I'm looking into now. |
I have fixed the crash on master. I'll look at 0.10.2 on Windows soon. |
Try as I might, I can't reproduce this on Windows 10 with 0.10.2. Can I get precise reproduction steps? |
Is the fix for the crash incorporated in the current 0.10.3 release? If yes, the bug is not fixed on version 0.10.3 on NixOS. If not, I would compile the master branch on my machine and test it. |
If it were, this bug would have been closed. I don't have a repro case for the 0.10.2 crash. The fix on master is for a different crash that only existed on master. That said, the backtrace you posted doesn't seem to be for 0.10.2--that line isn't in that function on that version. |
Just what the title says...
The text was updated successfully, but these errors were encountered: