BROKEN graphic after 'Save/Load state'...

[srcdabada]

Describe the bug

example game name is '河原崎家の一族'
the game outputs normally when using in-game save/load system.
but it sometimes outputs strange screens when using dosbox-x save/load state system.
when this problem occurs, the only solution is to reboot dosbox-x.
I don't know if the memory with the picture is missing during 'Save state' process, or if the memory is not loaded normally during 'Load state' process.
tested on the most recent release build,
DOSBox-X 2025.01.01 2025-01-01 08:24 win32,win64,SDL1,SDL2,vsbuild,mingw all.
used default copy of 'dosbox-x.reference.conf', not modified.

Steps to reproduce the behaviour

1. 'Save state' just before a specific choice branch of the game.
2. Choose one of the options, play the game for a little while, and then 'Load state'.
3. Choose another option and proceed with the game, a strange screen can be output.

Expected behavior

No response

What operating system(s) this bug have occurred on?

Windows 10 Pro 22H2 19045.5247

What version(s) of DOSBox-X have this bug?

DOSBox-X 2025.01.01 2025-01-01 08:24 win32,win64,SDL1,SDL2,vsbuild,mingw all

Used configuration

default copy of 'dosbox-x.reference.conf', not modified.

Output log

No response

Additional information

No response

Have you checked that no similar bug report(s) exist?

• I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

• I agree to follow the code of conduct and the contributing guidelines.

[joncampbell123]

Save states don't really save a whole lot at the moment. If the game uses files, XMS, EMS, and most PC-98 state, it isn't saved in the save state yet.

[srcdabada]

it works fine with 'DOSBox SVN Daum Ver 20150125'
I thought this was a bug because it was already working fine on fork 10 years ago.
I'm sorry to compare dosbox-x with other fork.

[joncampbell123]

The save state system is completely different from Daum, as is the emulation code.
It should definitely be improved.