Save states can crash RetroArch
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 77
- Forks
- 38
- Avg merge
- 36m
- Merged PRs (30d)
- 6
Description
Loading a save state affects the game's behavior and can even crash RetroArch, I think this is likely because 68K instructions are ignored by save states, which is not normal and 68K instructions are requried to be affected by savestates to make core stable.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Begin by reproducing the crash when loading a save state, then trace the save-state handling for 68K instructions and compare behavior before and after loading. Done means save states no longer alter game behavior unexpectedly or crash RetroArch, with a regression test covering the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100