[Bug] tee segfaults at common_scene_change (scene 0, title screen transition)

[RudideC]

Prerequisites

• I am confident that my issue has not been reported already in open OR closed issues.
• I am able to reliably reproduce the issue on the latest stable or canary version.
• I am not using an unofficial build (Flatpak, Emudeck, etc.).
• I am a silly goose and didn't read these boxes.
• I am a silly goose and DID read these boxes.

Description of the issue

Platform: macOS 14.5 (Apple M2, arm64)
Ryujinx version: 1.3.265 Canary
Game: Super Mario Maker 2 v3.0.3 (01009B90006DC000)
Issue: Ryujinx segfaults consistently at common_scene_change (scene 0, title screen transition) every run without exception.
Last log lines before crash:

ServicePrepo ProcessPlayReport: Room: common_scene_change, after_scene: 0, before_scene: -1
zsh: segmentation fault ./Ryujinx

What's been ruled out:

• Happens with and without mods loaded (but only happens with logging, when not logging to a file it works, but the mod never loads [open course world])
• Tested on 1.3.264 and 1.3.265
• Shader cache cleared, same result
• The game reaches the title screen transition and crashes during the GPU draw call for that scene (one run showed: "GPU processing thread is too slow, waiting on CPU..." immediately before the crash)

ryujinx_output.txt

Reproduction steps

Using OCW version 0.3 and Mario Maker 2 3.0.3, open the game with the emulator normally.
Now do the same thing, but open the emulator with the command: cd /Applications/Ryujinx.app/Contents/MacOS && ./Ryujinx 2>&1 | tee ~/Desktop/ryujinx_output.txt

Log file

Ryujinx_Canary_1.3.265_2026-03-16_12-13-10.log

OS

MacOS 14.5

Ryujinx version

1.3.265 Canary

Game version

3.0.3

CPU

M2 air

GPU

M2

RAM

16GB

List of applied mods

Open Course World v0.3

Additional context?

No response

[sh0inx]

Can you try disabling hypervisor and replicating?

[RudideC]

Can you try disabling hypervisor and replicating?

Hypervisor is disabled, the game doesn't even run with it enabled

[sh0inx]

1. We do not provide support for anyone using NSO alternatives. OCW is an NSO alternative, it allows you to connect to a server that the game normally would disallow if you did not have NSO, which puts it in direct competition.
2. This is kind of a non-issue, but I won't be closing it because it's likely related to the myriad of macOS issues we've been experiencing recently. Ryujinx already logs everything to a file in its directory, there is no need to use the tee command.

[RudideC]

1. We do not provide support for anyone using NSO alternatives. OCW is an NSO alternative, it allows you to connect to a server that the game normally would disallow if you did not have NSO, which puts it in direct competition.
2. This is kind of a non-issue, but I won't be closing it because it's likely related to the myriad of macOS issues we've been experiencing recently. Ryujinx already logs everything to a file in its directory, there is no need to use the tee command.

1. yeah, mb
2. i used the tee command because the logs never showed up