Dolphin core sporadically crashes entire program when playing Gamecube games

[grunt22fox]

I've been running into an issue that makes the Gamecube games on Retroarch completely unplayable, where it will start the game up for a random amount of time (could run from anywhere from literally no time at all to 5-10 minutes from what I've seen) and then crash outright forcing you to quit the program from it not responding. Interestingly enough I wasn't able to replicate this issue on my AMD laptop, where the games run completely fine under the same conditions and version but with a different CPU and GPU. The setup for my rig where the issues are happening are listed below:

OS: Windows 10 Home Build 21H1 CPU: Intel Core i5-7400 @ 3.00 GHz GPU: NVIDIA GeForce GTX 1060 3GB RAM: 16GB DDR4-2400 RAM

The issue persists when selecting multiple video drivers, going across DirectX 11, Vulkan, and OpenGL core. The latest log for when the program did this is below:

log.txt

[Sanaki]

I've experienced the same myself many times since January 24th (first reference I could find where I mentioned the issue in chat logs). I often can go as long as 30 minutes before the hard freeze occurs. Linux Mint 19.3 in my case, with an Nvidia card (GTX 1060 6GB). I've tried tracing the cause before, but I simply lack the experience to manage to do so in any helpful fashion.

[0yz]

Same problem here on Linux. I can sometimes play for 10 minutes straight and sometimes it dies within seconds. In my case it doesn't crash but it completely freezes requiring me to kill the process manually. My log looks the same as OP's, no errors/warnings.

My specs:

kma@plexserver:~$ screenfetch

         _,met$$$$$gg.           kma@plexserver
      ,g$$$$$$$$$$$$$$$P.        OS: Debian 11 bullseye
    ,g$$P""       """Y$$.".      Kernel: x86_64 Linux 5.10.0-9-amd64
   ,$$P'              `$$$.      Uptime: 4d 22h 13m
  ',$$P       ,ggs.     `$$b:    Packages: 3046
  `d$$'     ,$P"'   .    $$$     Shell: bash 5.1.4
   $$P      d$'     ,    $$P     Resolution: 1920x1080
   $$:      $$.   -    ,d$$'     DE: KDE 5.78.0 / Plasma 5.20.5
   $$\;      Y$b._   _,d$P'      WM: KWin
   Y$$.    `.`"Y$$$$P"'          GTK Theme: Breeze [GTK2/3]
   `$$b      "-.__               Icon Theme: BeautyLine
    `Y$$                         Disk: 2.1T / 6.2T (36%)
     `Y$$.                       CPU: Intel Core i5-3570T @ 4x 3.3GHz [47.0°C]
       `$$b.                     GPU: Quadro P400
         `Y$$b.                  RAM: 2683MiB / 7910MiB
            `"Y$b._             
                `""""           

[raymears]

Same issue here. Ubuntu 20.04. Can't post specs/ logs right now. It has saved me from a few hairy Mario Kart beatings by my daughter, but would rather it didn't happen on balance :)

[Sanaki]

While this issue still does exist, these days it usually only happens to me after around 16 hours. I'm not sure what's changed, and it's made trying to track it down almost impossible.

[jibarofoss]

It's happening to me as well on the libretro-dolphin-git package from AUR.

[marcecj]

I hit this pretty regularly (RetroArch freezes completely, no sound, no UI, forcing me to terminate it), and the actions the crashes correlate with varies to some degree over time. Here are my observations with with Ocarina of Time from "The Legend of Zelda: Collector's Edition" (I've only sporadically played other GameCube games):

• For a long time the crashes correlated with loading a game from a Samba share, but not from a local file. I disproved that idea by counterexample last night (and tonight), where RetroArch crashed consistently with a local ROM, too.
• Also a long-time correlate, a crash is very likely to happen when saving in-game.
• Also a long-time correlate, when a crash happens, it often happens right at the Nintendo logo, or shortly after in the game selection screen.
• Last night crashes clearly correlated with streaming on Discord, to the point that I could reliably start the game (>90%) as long as I stopped my Discord stream beforehand. Also, it seemed that the crashes happened (much) more often in specific types of scenarios, e.g., during cut scenes (3 or 4 times in a row after beating Phantom Ganondorf), in addition to the usual correlates of crashing right after launching the game (while the Nintendo logo is still being shown) and when saving in-game.
• Tonight RetroArch crashed no matter what, almost always at the loading screen. I only got the game to load 2 or 3 times, but it crashed within a few minutes each time.

As a result, I had to switch to standalone Dolphin, which hasn't crashed once.

I use the Flatpak version of RetroArch (Version: 1.19.1 (Git 0792144) Jul 14 2024 ) and the dolphin-emu core (Git version 89a4df7). Yesterday I tried a newer build of the Dolphin core provided to me over Discord here, but it didn't help. My system specs:

CPU: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz RAM: 32 GB DDR3 GPU: AMD Radeon RX 580 Series (RADV POLARIS10) OS: openSUSE Tumbleweed (version 20240810)

Here are all of my log files from tonight (I see I should redirect RetroArch's full output instead of relying on -v --log-file, which is how I created these, there's a lot missing, such as shader messages): retroarch_2024-08-11T22:43:13+02:00.log retroarch_2024-08-11T22:39:31+02:00.log retroarch_2024-08-11T22:38:17+02:00.log retroarch_2024-08-11T22:37:34+02:00.log retroarch_2024-08-11T22:36:41+02:00.log retroarch_2024-08-11T22:35:51+02:00.log retroarch_2024-08-11T22:35:03+02:00.log retroarch_2024-08-11T22:33:19+02:00.log retroarch_2024-08-11T22:27:49+02:00.log retroarch_2024-08-11T22:26:57+02:00.log retroarch_2024-08-11T22:25+02:00.log