1.19.2 Open GL Error spam
BlackTalons opened this issue ยท 6 comments
Tried the mod alone in Forge version 43.3.0, Java jre 18.0.2.101 hotspot. Upon entering a world, MultiMC log gets a constant, per frame spam of the following error:
[00:41:14] [Render thread/INFO] [mojang/GlDebug]: OpenGL debug message: id=1280, source=API, type=ERROR, severity=HIGH, message='GL error GL_INVALID_ENUM'
This has a significant impact in performance, specialy when compared with Rubidium with the same setup.
These errors look more likely to be related to GPU driver issues than something I can solve from within the mod itself. Please ensure your GPU drivers are up to date. For Nvidia and Intel in particular you may wish to refer to Sodium's FAQ.
I checked Rubidium on same map. Only changed mod, nothing else and is same bug. Weird. Because this problem did not occur before.
After updating the drivers, it seems to be OK. I checked many times whether the MC crash would happen quite quickly and now after the update I have been running for a long time and it doesn't crash.
Same here. Just moving around for testing after changed Rubidium on Embeddium.
1.19.2 43.3.2
[11:58:07] [Render thread/INFO] [mojang/GlDebug]: OpenGL debug message: id=0, source=API, type=ERROR, severity=HIGH, message='Unknown internal debug message. The NVIDIA OpenGL driver has encountered
an out of memory error. This application might
behave inconsistently and fail.
(pid=22752 javaw.exe 64bit)'
[11:58:07] [Render thread/INFO] [mojang/GlDebug]: OpenGL debug message: id=1285, source=API, type=ERROR, severity=HIGH, message='GL_OUT_OF_MEMORY error generated. Failed to allocate memory for buffer data.'
[11:58:07] [Render thread/INFO] [mojang/GlDebug]: OpenGL debug message: id=1281, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_VALUE error generated. Invalid size and/or offsets.'
[11:58:07] [Render thread/INFO] [mojang/GlDebug]: OpenGL debug message: id=1281, source=API, type=ERROR, severity=HIGH, message='GL_INVALID_VALUE error generated. Invalid size and/or offsets.'
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000024b11a9fa5a, pid=22752, tid=18224
#
# JRE version: OpenJDK Runtime Environment Microsoft-28056 (17.0.1+12) (build 17.0.1+12-LTS)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-28056 (17.0.1+12-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C 0x0000024b11a9fa5a
#
# No core dump will be written. Minidumps are not enabled by default on client versions of [Windows](url)
I can't reproduce this on my system. Other, similar reports on the Sodium issue tracker suggest this is linked to using overlay software (e.g. MSI Afterburner/RivaTuner) with Sodium.
