Emulator Issues #13825
closed
Memory widget not cleared on stop
0%
Description
Game Name?
Super Mario Sunshine
Game ID? (right click the game in the game list, Properties, Info tab)
GMSE01
MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)
0c6d2edae9fdf40dfc410ff1623e4119
What's the problem? Describe what went wrong.
When ending emulation, the currently visible values in the memory widget are no longer cleared. This happens even if the setting for auto-update is disabled. If you scroll up or down, the rest of memory is shown correctly as dashes.
What steps will reproduce the problem?
- Show the memory widget.
- Start a game.
- Stop the game. The memory widget will not be cleared.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes (2506-91)
Is the issue present in the latest release? For future reference, please also write down the version number of the latest release.
Yes (2506a)
If the issue isn't present in the latest release, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
2412-209
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel Core i3-4170 @3.70 GHz
Intel HD Graphics 4400
Windows 10 Home v22H2
Files
Updated by 
Updated by Amphitryon 11 months ago
- Is duplicate of Emulator Issues #13828: Unify debug widget behavior on stopping emulation added
Updated by Amphitryon 11 months ago
- Status changed from New to Duplicate
If the game itself crashes, it's still running, so you can view all of its memory as you like. If it's instead Dolphin that freezes or crashes (which happens all the time), the lack of clearing likewise doesn't help. So I definitely would prefer for it to be cleared. However, given the inconsistent behavior of all the debug widgets in this area, I've opened a new issue that is more comprehensive.