libretro / libretro/RetroArch

Loading retroarch.cfg Crashes RetroArch | Settings Don't Stick

Open
#14,109 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

When loading a retroarch.cfg file using the Load Configuration option RetroArch crashes, when the config file does load the settings don't appear to stick after restarting RetroArch.

Expected behavior

For RetroArch to load the .cfg file correctly and for the settings to remain changed after restarting RetroArch.

Actual behavior

RetroArch freezes then eventually crashes a few moments later, appears to be due to a menu driver conflict.

Steps to reproduce the bug

For the crash:

  1. Create a config file with a menu driver different to the one you're using.
  2. Load said config file.

For the settings:

  1. Create a config file with the same menu driver as the one you're using as well as an obvious change you could check has stuck such as the FPS counter.
  2. Load said config file.
  3. Restart RetroArch.
Bisect Results

It's been happening for as long as I can recall, seems to happen regardless of platform too.

Version/Commit
Environment information
  • OS: Windows 11 21H2 | Xbox Series X

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 Load Configuration flow with a config using a different menu driver, then investigate configuration loading and menu-driver handling. Also test whether a changed FPS counter setting remains after restarting RetroArch. Done means loading the configuration no longer freezes or crashes and its settings persist across restart.

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
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.