RetroArch icon indicating copy to clipboard operation
RetroArch copied to clipboard

Crashing when switching OBS scenes

Open Chromagram opened this issue 1 year ago • 3 comments

Description

Randomly, loading games on RetroArch or switching scenes in OBS that include RetroArch as a window capture causes RetroArch to just full crash.

Expected behavior

RetroArch should stay open without crashing when loading games or switching OBS scenes.

Actual behavior

Loading games (mostly noticing on N64) and switching scenes in OBS crashes RetroArch with no error messages.

Steps to reproduce the bug

  1. Open OBS Studio
  2. Open RetroArch to the main menu
  3. In OBS Studio, add RetroArch window as a window capture
  4. In OBS Studio, make a second scene that doesn't have RetroArch capture in it
  5. In RetroArch, load up a ROM (N64 I found happens most often) 6x. Sometimes randomly, this is where RetroArch crashes 6xx. If RetroArch hasn't crashed yet, in OBS Studio, switch between your two scenes until RetroArch crashes

Bisect Results

I found this started happening after I started streaming Donkey Kong 64 on my Twitch channel. Before that, I had used RetroArch for numerous other games on different cores and it never once crashed. I had also played Mario Party 1 on stream through RetroArch and it never crashed like this.

Since Donkey Kong 64 started causing the crashing issues, I tested Mario Party 2 as well, and it is now crashing in the same fashion.

Version/Commit

You can find this information under Information/System Information

  • RetroArch: 1.19.1

Environment information

  • OS: Windows 11 Home, 23H2, Build 22631.4391
  • OBS: 30.2.3 (if it helps)

Chromagram avatar Nov 02 '24 08:11 Chromagram

Anything I can take a look at or try? It's a continuous issue.

Chromagram avatar Nov 29 '24 06:11 Chromagram

First of all, please try to provide some logs.

Thank you.

gouchi avatar Dec 02 '24 13:12 gouchi

Hello, I tried to follow the instructions at the link, but I get this error message in PowerShell:

retroarch.exe : The term 'retroarch.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

  • retroarch.exe -v --log-file retroarch.log
  •   + CategoryInfo          : ObjectNotFound: (retroarch.exe:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    
    
    

Suggestion [3,General]: The command retroarch.exe was not found, but does exist in the current location. Windows PowerShell does not load commands from the current location by default. If you trust this command, instead type: ".\retroarch.exe". See "get-help about_Command_Precedence" for more details.

Anything I can try? Thank you. P.S. I should note that I have switched currently to playing a Game Boy Color game on stream, which doesn't have the crashing error. When I do figure out how to make a log, should I force a crash from the N64 core first, then take the log?

Chromagram avatar Dec 17 '24 13:12 Chromagram

Having this issue with N64 games too. Crashing seems to happen when OBS re-hooks the game. You can prevent a crash by using studio mode in OBS to keep the game hooked, but it's not ideal.

Also, crashes can seemingly be prevented by loading content with the Retroarch window visible in OBS, closing content, then loading it again.

Here's a log: retroarch.log

hazelwych avatar Jan 02 '25 01:01 hazelwych

Thanks for sharing more detailed scenario info on this. Hope this gets looked into.

Chromagram avatar Jan 30 '25 22:01 Chromagram