libretro / libretro/RetroArch

Crash on manual scan for MAME with mameinfo.dat file

Open
#13,026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

Using retroarch v1.9.9 and MAME (current) core (0.235), manually scanning a folder for roms and specifying the Arcade DAT file mameinfo.dat from this page retroarch crashes and no log information is generated about the crash, even if set to Debug.

Expected behavior

Retroarch should not crash and MAME playlist should be generated (ideally with the correct names).

Actual behavior

Retroarch crashes and it doesn't generate a log file that indicates any information about the crash.

Steps to reproduce the bug
  1. Import content -> Manual scan
  2. Content directory pointing to ROMS folder
  3. System name set to "MAME"
  4. Default Core set to "Arcade (MAME - Current)
  5. Scan recursively and Scan inside Archives set to "ON"
  6. Arcade DAT File pointing to mameinfo.dat file, downloaded from site above
  7. Start scan
  8. Retroarch crashes
Version/Commit
  • Build Date: Sep 6 2021
  • Version 1.9.9
  • Git Version: 36888612eb
Environment information
  • OS: Archlinux
  • Compiler: GCC(11.1.0) 64-bit (installed through pacman, I didn't compile it myself)

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

Start by reproducing the crash with RetroArch 1.9.9, the MAME current core, and the supplied mameinfo.dat during a manual scan. Inspect the available debug output and scan behavior; done means the scan completes without crashing and generates the MAME playlist.

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
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.