Crashing with Sodium + Distant Horizons on AMD Driver versions 22.Q3 and later.
Razaekel opened this issue ยท 3 comments
Version information
sodium-fabric-mc1.19.2-0.4.4+build.18
Reproduction Steps
GPU: AMD RX 6900XT
GPU Drivers (Crash): 22.Q3, 22.Q4, 22.10.2, 22.11.1
GPU Drivers (No Crash): 22.Q2
Minecraft Versions: 1.18.2, 1.19, 1.19.2
DH Versions: 1.6.5a, 1.6.9a, 1.7.0-dev
Sodium Versions: 0.4.1-build.15, 0.4.2-build.16, 0.4.4-build.18
Sodium Advanced Options - Chunk Arena Allocator: ASYNC
Sodium by itself does not crash. Distant Horizons by itself also does not crash. However, when both Sodium and Distant Horizons are used together, with rendering enabled in Distant Horizons, and the Chunk Arena Allocator in Sodium set to ASYNC while using any of the GPU Drivers (Crash), Minecraft crashes (either immediately or eventually), with nothing in the logs other than Process crashed with exitcode -1073741819. It also does not produce a crash report file.
Setting Chunk Arena Allocator to SYNC does not crash on any of the versions.
Using any of the above combinations with AMD Driver version 22.Q2, with the Arena Allocator set to ASYNC, Minecraft does not crash.
Crash Report file
No crash report files were produced from the crashes.
Additional information
I have also noticed that GPU usage is higher using the crashing driver versions, than the non-crashing driver version. The non-crashing driver will do 400-450 fps with 50-55% GPU usage, while the others will hit 90-100% around 100 fps.
Sometimes I will spot a corrupted chunk, and Minecraft immediately crashes right after.
Related Distant Horizons issue:
https://gitlab.com/jeseibel/minecraft-lod-mod/-/issues/450
I am having a simular issue, but my minecraft actually crashes fully. I am using Sodium Plus modpack. https://modrinth.com/modpack/sodiumplus
