mojira.dev
MC-229295

JVM crash when starting Minecraft (java.util.jar.Attributes.read)

Starting Minecraft Java 1.17 crashes on start every time, displaying error message that it exited with code 0. I am still able to play 1.16.5. I am also able to play 1.17 on a different computer, but not this one. I have tried uninstalling Minecraft launcher, deleting the .minecraft folder, and re-installing with no luck. Crash file is attached. I also checked for windows/drivers updates.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0000011d9804b3bc, pid=5740, tid=10596
#
# JRE version: OpenJDK Runtime Environment Microsoft-22300 (16.0.1+9) (build 16.0.1+9)
# Java VM: OpenJDK 64-Bit Server VM Microsoft-22300 (16.0.1+9, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# J 371% c1 java.util.jar.Attributes.read(Ljava/util/jar/Manifest$FastInputStream;[BLjava/lang/String;I)I java.base@16.0.1 (530 bytes) @ 0x0000011d9804b3bc [0x0000011d9804ae80+0x000000000000053c]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# If you would like to submit a bug report, please visit:
#   https://github.com/microsoft/openjdk/issues
#
---------------  T H R E A D  ---------------

Current thread (0x0000011d93c83950):  JavaThread "main" [_thread_in_Java, id=10596, stack(0x0000000ada500000,0x0000000ada600000)]

Stack: [0x0000000ada500000,0x0000000ada600000],  sp=0x0000000ada5fdac0,  free space=1014k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  0x0000011d9804b3bc


siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0xffffffffffffffff

Attachments

Comments 5

⚠️ Your bug report has been marked as private, as it contains some sensitive privacy information (e.g. an email address or session ID).

-- I am a bot. This action was performed automatically! If you think it was incorrect, please notify us on Discord or Reddit

I've redacted and reuploaded the attached log file.

Is this still an issue in 1.18.2 or snapshot 22w18a or later?

I have a similar problem on 1.18.2

I'm the originator of this issue and this game crash turned out to be an early symptom of a motherboard failure. This issue can be closed.

migrated

(Unassigned)

Plausible

Platform

Important

Crash

jvm-crash

1.17

22w18a

Retrieved