-
Notifications
You must be signed in to change notification settings - Fork 14
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
Bsnes cores crash 32bit Android RetroArch immediately on loading content. #2
Comments
Reposting my answer from libretro/RetroArch#12250 Crashing for me too on load content, with a Samsung Galaxy A5 2016 (it's a bit old, still running with Android 7, 32bit), I got a crash log by using
Tested with Super Mario World, I even added the BIOS files just in case but I don't think they're required for SMW. |
Safe to assume this only happens with 32bit Android installations of RetroArch. |
I analyzed the same crash for bsnes-hd some time ago. I didn't find a fix (I'm not a C++ or Android guy, so someone more skilled in the right areas will surely figure it out.). I did however find one piece of information that might help and also provides a workaround: The crash only happens with newer NDKs. Or rather it does work with the rather old Android NDK r20b (June 2019), see: As a temporary workaround you can probably use that build script with bsnes (or download the bsnes-hd Android ZIP if that works for you) if you are fine with manually installing the core. I hope the version information helps debugging this. |
Idk much about compilation stuff, even less about Android, but I redid some tests with the Libretro build environment with
So maybe it has something to do with that libco error that pops with -O1? 🤔 And yeah, as mentioned by DerKoun above, no crash when built with NDK 20.1.5948944 (r20b). |
Description
If you choose any of the bsnes cores and try to load content, RetroArch immediately crashes. Doesn't happen with Snes9x core.
Expected behavior
The content loads.
Actual behavior
RetroArch crashes.
Steps to reproduce the bug
Bisect Results
Happens with fresh install as well, and doesn't happen on Windows 10 20H2.
Version/Commit
You can find this information under Information/System Information
Environment information
Log
Log
The text was updated successfully, but these errors were encountered: