Emulator Issues #2973
closed
Reproducible crash in Metroid Prime 3
Added by krazubu over 14 years ago.
Relates to performance:
No
Relates to maintainability:
No
Description
What steps will reproduce the problem?
1.Play the game until the wrecked federal galactic station.
2.A few rooms inside, the game always crash when reaching a position
What is the expected output? What do you see instead?
Guess :)
Dolphin version with the problem? Other Dolphin version without the
problem?
Currently happens with 5950 to latest I tried (5981) can't say about olders.
32-bit or 64-bit and any other build parameters?
64 bit
OS version and versions of tools/libraries used?
Win 7
Please provide any additional information below.
I know this game is quite unstable with random crashes (not that often though), but I report that one because it's rather special in that it's not random so I thought it might be interesting to hunt. It's the 1st time I see such a crash happen on that game. Usually, you just do stuff again and it will pass where it crashed before, and/or will hang somewhere else. This one always happen at the same place in about 36% of the total game, whatever the plugins and options. That whole part of the game looks more unstable than the rest anyway.
Alas the panic handler doesn't come so I can't give much more info. If you need some more, just tell me how to get it. I have a working savestate just before but it's too big to upload.
you could take a look into the dolphin log file (which you might to delete sometimes cuz it can get pretty big ;) ) under Dolphin/User/Log (or something similar). There just look for the last entries after you've had that crash.
Nothing interesting in the log. I should have precised that it's a crash of Dolphin, not only the emulation. What I can give is the output of the crash window (see below) + and where visual studio debugger points (see pic).
Signature du problème :
Nom d’événement de problème: APPCRASH
Nom de l’application: Dolphin.exe
Version de l’application: 0.0.0.0
Horodatage de l’application: 4c4d9240
Nom du module par défaut: ntdll.dll
Version du module par défaut: 6.1.7600.16559
Horodateur du module par défaut: 4ba9b802
Code de l’exception: c0000005
Décalage de l’exception: 000000000004d036
Version du système: 6.1.7600.2.0.0.256.1
Identificateur de paramètres régionaux: 1036
Information supplémentaire n° 1: 4608
Information supplémentaire n° 2: 4608d3edd87d26e472b3d26561dba208
Information supplémentaire n° 3: 166f
Information supplémentaire n° 4: 166f72d0876dbec1f581c56c65c9bacf
Error reported by visual studio :
"Unhandled exception at 0x76f5d036 in Dolphin.exe: 0xC0000005: Access violation writing location 0x0000000000000038."
no wonder it doesn't work...it's all FRENCH! xD sorry, couldn't resist.
XD must be an incompatibility with the saucisson
Issue 3297 has been merged into this issue.
Issue 3149 has been merged into this issue.
Dolphin 3-177 fixed that hang, it's the only one that could pass that stage after waiting for more than 1 year. Probably related to icache invalidation introduced there (or the unwanted code clearing it triggered ?)
Tried many times to go to the place where it hanged, also after restarting the complete emu and it definitely doesn't hang anymore. In the worst case, the character sometimes turns himself into morph ball for unknown reason.
However on the next builds, the problem is back (icache invalidation has been removed).
Issues 3297 and 3149 shouldn't have been merged here, they are not the same problem. This crash wasn't the well known MP3 random crashs, it was a "stable crash" always happening at the same place when reaching some stage of the game.
So, you were on something with this icache invalidation code, it worth some refinment...
Thanks for the feedback. I am looking for ways to reintroduce the icache invalidation code without the constant code clearing.
still happens :(, i've tested with the 852fe9c4bebb version and... uknow
"the worst case, the character sometimes turns himself into morph ball for unknown reason"
Samus is a woman >_>
Jonathan, please test this with 3.0-195 or later.
it's still OK with build 199
- Status changed from New to Fixed
Also available in: Atom
PDF