[PS3] SNES games CANNOT be loaded with the same core TWICE or CRASH
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
This happens only with SNES games AFAIK: If you played for instance Rom A using SNES9X 2005, next time you load retroarch up, another core needs to be chosen, otherwise the PS3 hangs completely. Workaround is to always choose SNES9X 2005 PLUS or SNES9X 2010 (I always choose the second on the list). When choosing the same core as previously used, the system hangs while showing the message: LOADING FILE 1/2 (50%).
Expected behavior
Games should load with any core regardless of it being used before or not.
Actual behavior
System HANGS and PS3 needs to be reset.
Steps to reproduce the bug
- Load ROM A with SNES9X 2005 (or 2005 PLUS, or 2010)
- PLAY ROM A normally
- Quit RetroARCH (OPTIONAL)
- Load Retroarch again (OPTIONAL)
- Try to load same ROM A with SNES9X 2005 (or 2005 PLUS, or 2010) - has to be the same core as previous session.
- System hangs
Bisect Results
Since always. I started using on version 1.7.1
Version/Commit
You can find this information under Information/System Information
- RetroArch 1.8.1: still present
Environment information
- OS: PS3 REBUG 4.85 CEX
- Compiler: Pre built CEX bin
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue on RetroArch 1.8.1 with the listed PS3 REBUG 4.85 CEX environment, following the steps for loading the same SNES core twice. Investigate the load path reached at “LOADING FILE 1/2 (50%)”; done means the same ROM loads successfully with the previously used SNES9X core without hanging or requiring a reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100