Project

General

Profile

Actions

Emulator Issues #9316

open

Dolphin Crashes after save/load states

Added by eckso about 8 years ago. Updated over 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

ALL

What's the problem? Describe what went wrong.

Program crash after re-entering a game that used a load or save state function.

What steps will reproduce the problem?

Enter any game, load or save a savestate (using hotkeys here), exit with alt+F4, reenter any game.
Any backend.

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

I first pinpointed version 8400, it showed a crash dialog, some versions below it seemed fine. But now randomly tested version 7921 and got a crash, without dialogs, so my perception this a critical bug well buried in the code.

What are your PC specifications? (CPU, GPU, Operating System, more)

4670K, 750 Ti, Win7 SP1 x64

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

Would love to send a dump, as I'm getting loads of crashes recently, not related to this PR too.


Files

Dolphin.png (44.9 KB) Dolphin.png Background Processes eckso, 02/09/2016 07:06 PM
Actions #1

Updated by JMC4789 about 8 years ago

I believe this is a problem with certain Wii games. I get a lot of game crashes if I savestate, load the game, reopen the game and then load state immediately.

GameCube games I don't seem to have this issue with.

Actions #2

Updated by JMC4789 about 8 years ago

Or is this just a bug loading the game without loading a savestate? I'm unable to cause a crash using the methods you said without then loading the savestate after I reload the game.

Actions #3

Updated by eckso about 8 years ago

You only get the crash after you load the savestate on your second game run?

For me Dolphin gets totally unstable even after a simple savestate on the first game run. Sometimes just by exiting the game I get a crash dialog, or when closing the Dolphin program.

Either way, if you are getting crashes related to savestates I would consider them the same bug. Sometimes it doesn't crash, or not the same way, so the randomness of it is something to take into account.

If I'm not wrong I was also getting crashes on GC games. Let me do some exhaustive testings tomorrow.

Just in case, I'm still using nvidia driver v.353.30, if that helps.

Actions #4

Updated by JMC4789 about 8 years ago

Yeah, generally savestates are pretty stable for me as long as they were created in the same build of Dolphin. I wonder if your computer is, for some reason, hyper sensitive to dualcore even more than most users. I was reading through some of the issues you were having after last night and in most of those games I have no noticeable issues. So, I'm going to ask this: does the same instability pass to single core? Are you even using dualcore? It's just one of those things where I'm starting to get concerned that there's more going on here.

Actions #5

Updated by eckso about 8 years ago

I'm using single core since 2 weeks or more ago.
I also cleaned cached shaders, and no cross savestates...

Anyway tomorrow will test with a blank slate, last version, etc.
If you don't get the issues it smells as something external; driver, libraries, programs...
But I don't run anything out of the normal... and keep background process to a "minimum", so who knows.
Will report tomorrow.

Actions #6

Updated by eckso about 8 years ago

Ok, the problem is not related to savestates, it's simply that Dolphin is unstable as... Just enter a game, wait for title screen, Alt+F4, then close Dolphin program and you get a crash dialog.

The more things you do, the more screwed it gets (ie. exiting game and dolphin all at once when Alt+F4), call it savestates, etc And it occurs randomly, more frequent on both Mario Galaxies, but as I said, you can get the crash in others as well if you savestate, etc.

I tested with latest version rev. 8880. From blank config, and GFX settings (configured by hand on GUI). Turned off all my background processes (check screenshot).
So if you don't get the bug, then Dolphin might be crashing with something specific on my system, which in this case can only be libraries (I hate them but programs like Dolphin force you to install) or nvidia driver, which I just specified version above.

I'm done with testings until you implement some dump feature.

Dolphin.ini
http://pastebin.com/syUxCrtP
GFX.ini
http://pastebin.com/ZBinePdr

Actions #7

Updated by JMC4789 over 6 years ago

I can't reproduce any random crashing, and I've since played through Mario Galaxy 1/2

It's more likely that something else is interfering with Dolphin here. I just have no answer for you, and I wish I did.

Actions

Also available in: Atom PDF