libretro / libretro/RetroArch

Frequent invalid pointers crash retroarch when importing content

Open
#13,185 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug: scanner platform: linux scanner
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Description

Retroarch crashes when I import certain files and it's very hard to figure out why or how to stop it from happening

Expected behavior

just log the files that are breaky and skip them
or at least tell me which core I should uninstall or which file to delete

Actual behavior

Crashes with free() or invalid pointer error
Logging looks like this then bails

[INFO] CHD '/mnt/external/Emulation/roms/dc/King of Fighters, The - Dream Match 1999 (USA) (En,Ja,Es,Pt).chd' crc: 11524ba1
[INFO] Found disc label 'SLUS-01295'
[INFO] Found disc label 'SLUS-01296'
[INFO] Found disc label 'SLUS-01297'
[INFO] Found disc label 'SLUS-01251'
[INFO] Could not find compatible system.
[INFO] Found disc label 'SCSYSTEM'
[INFO] Could not find compatible system.
[INFO] Found disc label 'SCSYSTEM'
[INFO] Could not find compatible system.
[INFO] Found disc label 'SCSYSTEM'
[INFO] Could not find compatible system.
[INFO] Found disc label 'SCSYSTEM'
[INFO] Could not find compatible system.
[INFO] Found disc label 'PRODUCER'
[INFO] Could not find compatible system.
[INFO] Found disc label 'RRRRRRRR'
Steps to reproduce the bug
  1. retroarch --verbose
  2. Import content
  3. Browse to /mnt/external/Emulation/roms or path with files
  4. Import starts and goes for a while
  5. Crashes
Version/Commit
  • RetroArch: built Oct 31, abce5e1c6f
Environment information
  • Linux v5.14 x64
  • have tried with retroarch and retroarch-git from archlinux aur
  • compiled with latest GCC

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce with retroarch --verbose and the reported Linux content path, then use the import logs around the CHD and invalid-pointer failure to locate the responsible import path. Done means importing the affected files no longer crashes and the problematic files are logged and skipped, or the offending core or file is identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.