-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Several Cores Crash When input_max_users Set < 5 #3843
Comments
Found out this happens with the Mupen core too. I've found Banjo Kazooie works fine in both cores for some reason. Here's a backtrace:
|
Ok, I should have tested multiple cores first. I just tested glupen not working and desmume working and thought it was something with glupen, but several cores are crashing. Working cores: mGBA, mednafen-wonderswan, Desmume, gambatte, Picodrive, Genesis Plus GX, mednafen-saturn, mednafen-psx, mednafen-ngp, PPSSPP, BSNES-Mercury Balanced. Edit: Here are backtraces for the last three crashing cores: |
Have you tried to bisect RetroArch? Or at least tested with 1.3.6? |
I think it's happening in reicast too |
I don't have the stuff to bisect, but at least it seems to have started somewhere after a build from the 20th. |
I just tested up-to-date mupen and RetroArch and I couldn't reproduce Are you running insider builds? |
No, I'm on stable anniversary with all the latest cumulative updates. No problems with my controller or Steam. |
Ok, seems setting input_max_users to anything less than 5 results in a crash for certain cores. |
Someone reported this same issue on Vita a few days ago. I figured it was Vita-specific, but evidently not. |
I was able to reproduce this - From this point on, it no longer crashes for me on Linux with Mupen64plus when I set max users to 1. Try to see if it fixes it on all other platforms as well. |
Confirmed! I apparently have this problem. I can't play a NES game (Nestopia) with anything below 4 on input-max_users... on Archlinux. I assume my config was awful. I had it at 1. Not related. If you set input_max_users to 20~ or above, it'll crash. Necessary 4 for Nestopia. |
Instead of saying 'confirmed', at least test if it happens with the latest sources. |
Noted. This happened with the latest sources. |
Which input driver/joypad driver are you using, and give me an exact scenario to reproduce this. |
I start with I start with no retroarch.cfg. I didn't explicitly set any input/joypad driver. It is... Navigate to start a random game or pick something from history. I picked something from history. If it didn't start, then that's it. Repeat with a new higher number until the game eventually starts. |
Which core do you get this crash with? Be specific. I can't reproduce these issues anymore on my end with udev/udev drivers. |
All cores came from Online Updaters. I will try the cores that I recently got from ./libretro-install.sh right now. |
Cannot reproduce with Nestopia anymore. I think you don't have the latest nightly built from source, it simply cannot happen anymore after my recent commits. |
I install |
It has nothing to do with the cores. Look, you are not being specific here again. Are you compiling it directly from source or not? It's a very simple question really. You are only adding to the confusion here by not being directly specific here. |
I thought using retroarch-git was the latest source. It looks like it might not be. I tested it with |
Your log above shows you were on an old build. |
YES.
NOW.
Necessary max_input 4 for Nestopia. // Works with 1 👍 PROBLEM SOLVED? 👍 I notice this different issue just now... Try typing 'x' in search prompt. It comes up x1. |
The x/z issue is known for now. It will require several input code changes in order to fix that. Anyway, that is a different issue, open a different issue for that if one doesn't already exist. |
Sure! I will file it under the "z" issue I made. Sorry I never knew about x. |
On windows with the latest buildbot build (b1d1875) SuperGrafx and Nestopia now work with input_max_users = "2", but Glupen64 and MAME 2015 are still crashing. MAME 2015 backtrace:
Glupen64 backtrace:
They will both work if I set max_users to at least 4 now. |
Test if this fixes it - |
Everything works fine with it set to 2 or 1 now. Thanks! |
I'm getting a crash with this core when loading content on today's nightly (10/22). It doesn't happen in the previous one available on the buildbot (10/20). A bt in gdb gives me:
The text was updated successfully, but these errors were encountered: