Retroarch crashes when adding roms from archives
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Is there an existing issue for this?
- This is a bug in RetroArch frontend
- I have searched the existing issues
Description
When adding games from an archive (I tested 7z and Zip so far), Retroarch crashes without any error.
This happened beginning with version 1.22.0 while scanning 7zip or Zip files for ROMS.
These archives are not corrupted and I was able to extract them normally to test this.
However, on version 1.21.0, scanning the same compressed archives worked.
Expected behavior
Scanning compressed archives are added to the according playlist and Retroarch doesn't crash.
Steps to reproduce the bug
- Have Retroarch 1.22.2 installed
- Try to add ROMS from a highly compressed 7z or Zip file containing ≈800+ files
- Retroarch crashes after a certain amount of scanned files
Version/Commit
1.22.0, 1.22.1, 1.22.2
Bisect Results
1.21.0
Present in the nightly version
I don't know
Platform & operating system
MacOS Tahoe 26.5.1
Affected Cores
No response
Environment information
- M4 MacBook Air
- Current Retroarch 1.22.2 Stable Build
Relevant log output
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 crash on macOS with RetroArch 1.22.2 using a highly compressed 7z or Zip archive containing about 800 files, noting that no log output is provided. Compare the scan with version 1.21.0 and investigate the regression between those versions. Done means archive scanning completes without crashing and the ROMs are added to the appropriate playlist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100