Emulator

Game Name?

Super Mario Sunshine (this doesn't seem to be only that game though, Super Paper Mario also had this problem)

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, info tab, MD5 Hash: Compute)

0c6d2edae9fdf40dfc410ff1623e4119

What's the problem? Describe what went wrong.

Since Dolphin 5.0-2178 ( https://dolphin-emu.org/download/dev/5da565a1a1b3b148a41a483e1052f31b5698cf3c/ ), the emulator will crash upon adding any memory breakpoints and then let the game run for a little (less than a second). It doesn't matter if the emulator was paused or not, when it runs with the new memory breakpoint, it will crash. This version was the result of a bisection I performed which lead to this particular commit which would have introduced the crash:

https://github.com/dolphin-emu/dolphin/pull/4735/commits/f31b25fe3934b899a00fb049b3c45740c67b11b7

I mainly tested this on Super Mario Sunshine, but I first encountered the issue on Super Paper Mario leading me to think (and considering the commit is jit related) that this issues would at least apply to many or all games.

What steps will reproduce the problem?

1 Start Super Mario Sunshine on Dolphin 5.0-2178 or newer in debug mode
2 Add a memory breakpoint (using the breakpoint panel) with the following ooptions:

With an address: 80000000
Action: Write
Flags: Break and Log

3 Upon clicking OK, the game should crash shortly after if it is running (if it isn't, pressing play will trigger the crash the same way)

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 encountered the issue on Dolphin 5.0-2577, then I didn't encountered it on Dolphin 5.0-1880 so I did a git bisect from there. That lead me to the above versions and commits.

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

Arch Linux
Intel core i5 4690 3.5 Ghz
Intel HD Graphics 4600 (using Mesa 17)
8Gb RAM

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

GDB didn't helped, I got this on single core and as for why I used 80000000 as a test address, it';s because normally, games don't write there and when the creation of a memory breakpoint is sucessfull, the emulator would decrease its performance without any crashes. This just allowed me to see this effect better, but I also tried the address 8040CE30 which is the RNG seed to be sure. On that address, versions before 5.0-2178 behaves normally while you get the crash otherwise.