RetroArch crashes or freezes

Separate the two kinds of crash

RetroArch failing tells you very little on its own, because the program is a shell around cores. Split the problem first:

• Crashes on launch, before any menu — the video driver or the config file is broken.
• Crashes when a specific core loads a specific game — the core is at fault.
• Freezes when the menu opens — a known overlay/menu state bug, not a core problem.
• Crashes only after fast-forward — Vsync plus a Vulkan swapchain that cannot keep up.

Knowing which one you have removes most of the guesswork.

Rule out the driver

1. Update RetroArch itself before anything else — these are recent regressions, and several are already fixed.
2. Open Settings → Drivers → Video and switch between Vulkan and GL (on macOS, Metal). Launch a core after each change.
3. Turn Vsync off temporarily and repeat whatever triggered the crash, especially if fast-forward was involved.
4. Disable auto-load state while testing. A state saved by an older core build can crash a newer one on load, which looks like a random crash.

Rule out the core

Load one core, one game, and nothing else. If it survives ten minutes, move to the next core. This is slow but it is the only way to find a single bad core among dozens.

The tracker has concrete examples worth recognising: a Vulkan crash triggered by Vsync during fast-forward, the on-screen menu hanging the UI and hiding playlists, and Dolphin core crashing while loading an auto-save state. All three are core or driver interactions rather than hardware faults.

When it’s the config file

A corrupt retroarch.cfg produces a crash on every launch with no menu at all. Rename it (do not delete it), start RetroArch so it regenerates a default, and confirm it opens. Then restore your settings a section at a time.