Emulator Issues #206
Saving/Loading savestate crashes Dolphin
What steps will reproduce the problem?
1. Save your game using a savestate (if the game didn't crash proceed to step2)
2. Load your savestate
What is the expected output? What do you see instead?
Saving should save, and loading should load. When saving, sometimes the
emulator crashes, hangs, or shuts down. Same thing with loading.
What version of the product are you using? On what operating system?
r704 32bits, Windows XP SP3
Please provide any additional information below.
You can reproduce this at all times if you save Super Smash Brothers Melee
(US) during combat, and if you were lucky enough for it not to crash, don't
worry, because loading will hang/crash/close it for sure.
#10 Updated by memberTwo.mb2 over 11 years ago
First of all, you do great job federelli... +1 for you ;)
Well... I don't think it's very usefull but I don't get where did you found those
"common errors". In the fifo desync popup (GX illegal command) or before in debug?
BTW, DC need serious fixes to enable correctly savestates and more. But for now, let
say that in DC there is one small part of the state that isn't sync with the other
part. That's obviously the problem :p.
#11 Updated by federelli over 11 years ago
Yeah i understand what you mean, thanks for the compliment :), but reporting issues
is nowhere near fixing them.
What i mean with common errors is the kind of error i get when the emulator crashes
upon saving/loading a state. For example:
GFX: Unknown Opcode (0x62)
Illegal Command 62
I can only begin to imagine the amounts of things that need to be saved in order to
save a state, while keeping the emulator synced and writing 15+ MB files to the HD,
and even after that, restoring said state, mantaining sync once again.
#14 Updated by memberTwo.mb2 over 11 years ago
savestates don't work for me in MP1 (intro movie + menus) DC on and DC off. I wonder
if it use to work in SC before my datareader change... r729 (TOCHECK).
Guys? Reports if you have any savestate issue in SC mode please (infos: rev + games +
#16 Updated by XTra.KrazzY about 11 years ago
- Status changed from Work started to Fixed
AFAIK, I made savestates work even when saving on DC and loading on SC, and vice
versa. When loading a state crashes the emulator for a reason, it might be because
now the GPU resets the BP memory (which is good) after loading a state and 'dirties'
some wrong address which should be added (as with 0x40,0x65 and so on)
Until someone says otherwise, this issue is fixed.
#24 Updated by kmmng1 about 11 years ago
Single core mode also causes crashes.
It's too difficult for me to track the exact revision, I cannot download and compile
every revision possible, but it should be between 1577 and 1634, because 1577 worked
for me, and 1634 and more higher revisions I tried, all caused the same crash.
#35 Updated by federelli almost 11 years ago
r2195 tried saving Zelda (both), Metroid 1/2, RE0/1, MGS: TS.
If they don't crash while saving, they crash/hang while loading, sometimes it works
sometimes it doesn't. Seems to work better when there's no 3D (like during logos and
No error messages.
#40 Updated by sl1nk3.s almost 11 years ago
hmm... it works great in WW for me, i'm using DC
there's still some problems though, Metroid Prime doesn't work fine with savestates,
it saves (also takes more time than saving in WW) but when you load the savestate, it
crashes. And for some reasons, it's fine in SC mode..
#46 Updated by marcus almost 11 years ago
yes. always same rev. you say infinitely...have you tried holding down the enter
key? It did that at one point during paper mario, but holding enter down for about 5
secs and going through seemingly endless opcode errors made the game continue like
nothing had happened.
#57 Updated by gabrielmorano over 10 years ago
here is a picture of the messages
"Internal LZO error" so far has only appeared on few games (like shadow the hedgehog)
the other 2 issues happens on every single game, Specially "metroid prime's"
issue is presented no mather the version x32 or x64 and no matter the config you use
(dual core on/off iddle skip on/off ... etc)
#59 Updated by federelli over 10 years ago
Saving is somewhat better now, but still unstable, it crashes the emulator but much
It's nice to get a warning when you are trying to load a savestate from another game.
Saving on videos still doesn't work.
Loading is as usual, sometimes it loads the save, sometimes it crashes the emu.
#60 Updated by gabrielmorano over 10 years ago
much less?? Oo
metroid prime's games are impossible to save with this method (well you can use the
savestate sometimes without getting a crash, but loading will surelly crash it)
what i noticed is that the emulator saves a lil bit better when the cammera is
focused on one point (like for example in Morph ball mode or in 2d games)
#76 Updated by gabrielmorano over 10 years ago
Metroid prime does not ramdomly crash (i played the whole game without problems but
the savestate problem.
Issue still happens in version r3661 x86 x64
and i tested it with a bunch of games (such as megaman network transmition, shadow
the hedgeog, metroid prime, castlevania judment, and a few more "still testing" games)
now it does not crash as ofthen while savingstates, bu loading states will hang the
emulation most of the times...
#81 Updated by gabrielmorano over 10 years ago
believe me it's not working....
for example while i was testing metal gear solid control issue. the times i used
savestate and loaded the emulator did 2 things
or either it gets stuck (music playing) and black screen or previous screen (freezed)
or directly the load works but then afther you move the emulator closes...
so still not working (i set metal gear as an option cuz i was playing the whole game,
but it also happens in a few more game i tested such as megaman network transmition,
metroid prime 3 etc...)
#82 Updated by federelli over 10 years ago
Found out something really important i believe.
Chances of the emulator crashing when it needs to create the savestate file are around
90% in stables games such as Z:WW. In the same game, savestating to an already creted
file will never ever hang the emu, hell, not even keeping shift+f# makes it hang/crash
(although memory consumption starts going up fast).
Sump up: Savestating will almost always crash if it needs to create a file from zero.
#86 Updated by Speeddymon over 10 years ago
Saving works fine here in DC mode, haven't tried SC mode yet (on Pikmin GC NTSC-US).
Loading worked up to r4365, but loading a saved state causes black screen and sound
loop freeze with both SC and DC mode, in r4366 and after r4375 or r4379 it causes the
emulator to fully crash, at least in DC mode.
#87 Updated by sl1nk3.s over 10 years ago
Using Save States between revisions is not -always- going to work unfortunately,
actually it depends on the change, but its not to be trusted, also there should be a
nice windows telling you that your savestate is not compatible, but it seems like
nobody cares to update the save state revision :P
#92 Updated by romanodj over 10 years ago
game Zelda wind waker
save state created with rev 4434 (loads fine)
r4425 = loads fine
r4435 = loads fine
r4447,r4450,r4460,r4466 = no way loading LoL = when I select the file and click
"open", the emulator just "disappear" (closes with no error messages)
xp sp3 32bits
and if it helps, here comes my ini files from /user/config
#95 Updated by gabrielmorano over 10 years ago
I haven't experienced a crash nor saving or loading states on the last revisions
since r3972 BUT most of the times when i try to Load a savestate this end up going
wrong and instead of taking you to the exact point you saved it does nothing (just
the music plays as if you where in the place you saved, but the screen is freezed and
no command is inputed either "example if you where against an enemy you will notice
the action is not going on cuz there is no sound of struggle etc..." just the
background music and the screen freezed)
tested it on a lot of games (and doing it more than once to see if it's fixed by
stresskey... but no)
another problem is with wii games that uses wiimote (I do not have a wiimote so i
don't know it this happens with a real wiimote, I tested it on wiimote pluggin
Once you load a savestate most of the times you will get a "disconnect" from the
wiimote and there is no way for you to Re-connect it.... so even if you have a
savestate you can't continue due to loading the state makes imposible for you to
move... ergo you can't continue the game. tested this on "Dead Rising" and "Metroid
last revisions I Tried where: r3972 x64 x32 and r4460 x64 x32
#97 Updated by XTra.KrazzY over 10 years ago
Well I haven't got a savestate crash for a while now. I do get the black screens
though and end up restarting dolphin and reloading. This is probably due to a deadlock.
ryan.hunt.44: This is not the savestate issue, but the wiimote desync issue, which we
should also solve for savestates to work properly on the Wii.
#111 Updated by gabrielmorano over 9 years ago
it's NOT that ofthen, but it does still happen... you need to save in different slots in order to be "safe" from corrupting the savestate and not been abble to use it, as when it saves as the emulator crashes the safe file becames sort of "invalid"
so the issue remains (just now is more stable)
last revision i tested was r6025 x64 and x32
(i don't know if this is relevant, but it seems to happen more ofthen with WAD games)
#113 Updated by gabrielmorano over 9 years ago
I used booth pluggins to test this and it does not change the rate of crashing it simply does no matter wich one you use and as frequently.
they do not need mmu (but you can use it if you want, it wont change)
for where it crashed is not an specific place, it happens around most games (specially if you stress the savestate) try on megaman 9 & 10, Castlevania The Adventure Rebirth, Contra Rebirth, Metroid Prime 3, Dead Rising.
like i said it does not happen in an specific place, but start saving over andover and most surelly by the 3rd or 4th time you save it will happen (if not i will try to make a video)
#114 Updated by jessestamm27 over 9 years ago
This is still an issue... I'm using Dolphin 2 r6205 SSSE3 x32, Dual Core enabled, D3D9 plugin, Dolphin Wiimote New Incomplete plugin, playing on Megaman 9.wad and Megaman 10.wad. I've experienced this problem with both KEYBOARD and USB Controller configurations for the Wiimote plugin.
In my case:
A 'crash' still leaves the video and audio playing but the input/controls are disabled, even after refreshing the input source in the wiimote settings
Saving a new save state will NOT ALWAYS crash the game
Loading a 'valid' save state will NOT USUALLY crash the game
Loading an 'invalid' save state will ALWAYS crash the game
I've had some great save states that I save with no issues only to find that when loaded, they are unable to be played (controls/input do not respond). This is repeatable.
#117 Updated by federelli over 9 years ago
The Metroid games are particularly thread unsafe for some reason, Metroid Prime 3 over all.
Sometimes you save and it saves fine but then it crashes 3-5 seconds after loading.
Sometimes it saves and you load and you get a black screen with sound.
Sometimes it saves and you load and you get nothing.
Sometimes it saves and you load and you get a crash.
Sometimes it doesn't even save and you get a crash.