libretro / libretro/RetroArch

[Steam] Crash When Loading PS1 Save States (Updated)

Open
#12,463 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

core bugs - not retroarch bugs platform: steam platform: windows savestates
Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

RetroArch version 1.9.3 & 1.9.4 can no longer load PS1 save states. This issue was not present in RetroArch version 1.9.2. This isn't a core related issue as the PS1 core version is still the same after updating RetroArch through Steam. Once I noticed this issue I installed an archived version of 1.9.2 for testing. I noticed that creating PS1 save states on 1.9.3 & 1.9.4 where fine, but loading these states on those versions would crash RetroArch instantly. I proceeded to copy over these save states to 1.9.2 and they where able to load just fine. I also tried the reverse by creating a PS1 save state in 1.9.2, and then loading these states in 1.9.3 & 1.9.4. The same loading state crashing issue happened. It should be noted that this only effects PS1 save states. All other save states will load without issue.

I went to the Steam forums to see if I could find info for a fix. I was asked to change video settings from GL to Vulkan. Then made the same tests as stated about. Sadly this did not fix the issue, and the loading of PS1 save states still crashes RetroArch. I will provide pastebin links to the logs below to help keep this post short.

Log when using GL: https://pastebin.com/UqJAZa94
Log when using Vulkan: https://pastebin.com/LACttzzS

System Specs:
Windows 10 64x
AMD Ryzen 7 3800X 8-Core Processor
XFX AMD Radeon RX 570 RS Black Edition 8GB
ROG Strix B550-F Gaming
Corsair Vengeance LPX 16 GB (2x 8GB)
Samsung 970 EVO 1TB NVMe M.2

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 the crash by loading PS1 save states created in both RetroArch 1.9.2 and 1.9.3 or 1.9.4, then compare behavior under GL and Vulkan. Start with the linked GL and Vulkan logs and isolate the version-specific loading regression; done means PS1 save states load without crashing while other save-state behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
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.