Citra on macOS crashes on subsequent rom loads

Issue:
citra will load a rom once but any time I try to load that same game a subsequent time the whole application crashes. I have to fully uninstall the app to get the same game to load twice.

System Information

  • Operating System: macOS Catalina 10.15.7
  • CPU: AMD Ryzen 7 3700X 8-Core Processor | AVX2 | FMA
  • GPU: Radeon RX 5700 XT 8GB
  • Citra Version (found in title bar): Nightly 1721
  • Game: any
  • Screenshot of Issue (include the full Citra window including titlebar): not applicable

Diagnostic Log
Attached

citra_log.txt (6.0 KB)

System Information for Support

Client Version                                Nightly 1721 HEAD-89410c1
Operating System                              macOS 10.15
CPU                                           AMD Ryzen 7 3700X 8-Core Processor              | AVX2 | FMA
Graphics API                                  OpenGL ?
Graphics Renderer                             ?
CPU JIT                                       [x]
Hardware Renderer                             [x]
Hardware Shader                               [x]
Hardware Shader, Accurate Multiplication      [x]
Shader JIT                                    [x]
System Region                                 -1
Shader Disk Cache                             [x]

I did not find anything wrong in your log file. Please wait for a moderator to assist.

Disable the Disk Shader Cache in Citra>Preferences>Graphics>Advanced Tab.

wow. yes that seems to have done the trick. is there a faq somewhere that I missed where I should have caught that setting?

No, this issue is something that occurs on some MacOS versions. Has to do with Apple routinely axing support for this and that and us not wanting to bother adjusting our code or information to their whims. For example, High Sierra used to run Citra just fine, until they cut support for something vital, now it doesn’t run at all (users are forced to use an older Citra version). Big Sur introduced specific issues with Hardware Shaders, so on so forth.
TLDR, not your fault, blame Apple.

1 Like