Setting mesa_glthread to true crashes Minecraft when Sodium optimisation mod is enabled.
System Info
- OS: Arch Linux
- GPU: TigerLake-LP GT2 [Iris Xe Graphics], and NVIDIA Quadro T500 Mobile (Optimus)
- Kernel version: 5.15.6-arch2-1
- Mesa version: 4.6 (Compatibility Profile) Mesa 21.3.0
- Xserver version (if applicable): 1.21.1.1
- Desktop manager and compositor: KDE Plasma, KWIN
Describe the issue
Setting the environment variable mesa_glthread=true
, when launching Minecraft with Sodium, causes Java to crash shortly after loading up a world. The same crash can not be reproduced without setting said variable. This is using MultiMC as a launcher.
Log files as attachment
Entire dmesg up until crash: dmesg.log
MultiMC log up until crash: minecraft.log
The SystemD Journal entry of the java crash: systemd.log
Any extra information would be greatly appreciated
I first took this issue to the developers of Sodium, however it seems it outside of their control, as they reported that they had issues with this setting in the past, and it seemed to them like an upstream issue. https://github.com/CaffeineMC/sodium-fabric/issues/1029
It seems like with this merge request: !13947 (merged), mesa_glthread=true
will be set by default for all mesa users playing Minecraft through the official launcher. This will cause a problem for anyone using the mesa drivers as well as Sodium, as the game would crash shortly after loading a world. Sodium is a rather popular optimisation mod, and such crashes would likely effect a good number of users. (All assuming this isn't only a me problem)
The crash seems to occur only after a few minutes of gameplay. Yesterday I was experiencing crashes with this setting after a few seconds of loading in a world.