2.3.0-b-dev M2 Max consistent & reproducible client crash

Hey, I have a dedicated server running fabric 1.20.1. We have multiple players. One has been having difficulties with DH & joining the server. If DH rendering is disabled, they are able to join the server and then even re-enable DH rendering. However, if they join with DH enabled outright they receive a full game crash. I will gather logs, but roughly it mentioned OPENGL buffer issues.
5 Replies
⁂ bradley
⁂ bradleyOP3mo ago
This happened on RC1 & still happens on RC2 after server & client full OS reboots the crash on the client seems pretty catasrophic, java VM level.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00000001eae0a7b4, pid=2713, tid=259
#
# JRE version: OpenJDK Runtime Environment Microsoft-8035246 (17.0.8+7) (build 17.0.8+7-LTS)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-8035246 (17.0.8+7-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)
# Problematic frame:
# C [GLEngine+0x11e7b4] gleRunVertexSubmitImmediate+0x19c8
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/kevinchung/Library/Application Support/PrismLauncher/instances/1/minecraft/hs_err_pid2713.log
#
# If you would like to submit a bug report, please visit:
# https://aka.ms/minecraftjavacrashes
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Process crashed with exitcode 6.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00000001eae0a7b4, pid=2713, tid=259
#
# JRE version: OpenJDK Runtime Environment Microsoft-8035246 (17.0.8+7) (build 17.0.8+7-LTS)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-8035246 (17.0.8+7-LTS, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64)
# Problematic frame:
# C [GLEngine+0x11e7b4] gleRunVertexSubmitImmediate+0x19c8
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/kevinchung/Library/Application Support/PrismLauncher/instances/1/minecraft/hs_err_pid2713.log
#
# If you would like to submit a bug report, please visit:
# https://aka.ms/minecraftjavacrashes
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Process crashed with exitcode 6.
one of the crash messages
Puhpine
Puhpine3mo ago
Can you also send the crash report and or logs?
⁂ bradley
⁂ bradleyOP3mo ago
The above message is in the minecraft logs. It is a system-level crash and no stacktrace is given.
Tactichu
Tactichu5w ago
Not to necropost, but im also consistently having the same issue, M2 Pro, running the nightly build, identical crash log.
Puhpine
Puhpine5w ago
try disabling instanced rendering in DH's settings using the nightly build. thats located somewhere in the graphics section, under generic rendering. if that doesnt work, bug apple about adding better openGL support

Did you find this page helpful?