Fatal Error in GC (SuspendThread Loop failed)
available in future release
Log In
Rexen²
I cleared my cached and while it hasn't fix the issue fully that seems to make the crash happen less.
StormRel
Merged in a post:
Fatal error in GC SuspendThread loop failed
King․ Ddraig
I open VRChat, and within 1-2 minutes I get this error pop up, and crashes to desktop, playing through Steam Proton on linux mint
Khloe_vr
The latest version of VRChat crashes with the error “SuspendThread loop failed,” I'm using Unity 6000.0.67f1-DWR_6158d48dc694.
On Linux Ubuntu 26.04.1
It crashes in GE-proton, Proton RTSP, and Proton Standard 11.0
Before the update, there were no problems with the game.
Photo Viewer
View photos in a modal
DerpyEagle
Was suffering this issue bad today on a 9950X3D2 with Arch, native Steam, latest kernel & drivers, with any versions of Proton. Couldn't consistently change worlds, open menus, or stay in a world for too long before getting the SuspendThread crash.
Disabling Esync and Fsync seemed to fix it for me. Set your VRC launch options to:
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
This will likely cause a performance hit but I had no crashes in 3 hours after setting this when previously I would crash within minutes. Hoping it helps someone else. Also hoping we get whatever release this fix is coming to soon...
arxmodeus
DerpyEagle This allowed me to use VRChat long enough to go to other worlds and muck around a bit at least. Will give longer test later. Many thanks if this is the silver bullet!
Ｆｅｌｌ
DerpyEagle This inspired me to check if NTSync is enabled. NTSync is the newer in-kernel replacement for ESync/FSync. It wasn't enabled.
To check:
ls -l /dev/ntsync
(if this file exists it's enabled)To enable it:
sudo modprobe ntsync
To enable it on future reboots:
echo ntsync | sudo tee /etc/modules-load.d/ntsync.conf
With this, I could play for over an hour without issues.
Ｆｅｌｌ
I don't actually think it's related to X3D chips anymore. We're getting it consistently on a 3900X (Mint Cinnamon) but not at all on a 5800X3D (Arch KDE Plasma)
AlexTaco-Anton
This issue appeared firstly in the
unity-6
beta branch and then continued to progress in the open-beta
branch after merging the unity-6
beta branch after announcing it was ready for merging.Distribution doesn't matter in this case because fault is the same on different setups and use cases.
I can only suggest (and guess) using the
git bisect
5 patches before merging unity-6
into open-beta
and 2 patches after merging.Distribution:
Debian Forky/sid
.Graphical environment: KDE on Wayland.
Steam installation: Non-flatpak.
Proton: 11 RTSP Fork.
SLR: steamrt4.
Architecture: AMD64
All information about the fault has already been sent by the Unity crash handler.
The issue is already in the
release
branch.Seefzi
This is not fixed lol, at least not on Linux systems.
Lygh's workaround but linux version:
get stress-ng from your distro's package manager
stress-ng --cpu 0 --timeout 60s
wait 10 seconds and start VRChat
this doesn't even work consistently so idk
arxmodeus
Happens to me on the release build, no matter Proton, GE or RTSP
'SELICA'
had this problem that crashed my game after two minutes after launchin game and just alt tab from game on another app on Debian 13 on Laptop with Ryzen 7 5800u
King․ Ddraig
I also made a post for this with the newest patch (1919), but the game actually loads for me and then crashes with this after about 1-2 minutes
Load More
→