TASEmulators / TASEmulators/BizHawk
Genesis - crash when loading a state for a different controller configuration
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Open a Genesis game
Make a savestate
Open settings and change Use 6 button controller
Reboot core
Loadstate
It crashes with:
System.InvalidOperationException: Memory consistency check failed. Is this savestate from different SyncSettings?
No doubt many cores have this problem, and maybe the state should work, and the error message is useful. However, it should be a pop up, then the loadstate should fail. Rather than completely crashing the emulator
Contributor guide
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
Reproduce the Genesis savestate sequence using the 6-button controller setting and capture where the System.InvalidOperationException escapes during loadstate. Trace the loadstate error-handling entry point; done means a SyncSettings mismatch shows a popup and cleanly rejects the state without crashing the emulator.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100