microsoft/openjdk

Access Violation When Launching Minecraft

mkZH0740 opened this issue · 1 comments

Describe the bug
I am using the bundled jdk in minecraft legacy launcher to launch vanilla minecraft 1.18.2. The game won't start and crashes with EXCEPTION_ACCESS_VIOLATION exception.

Desktop (please complete the following information):

OS & version [e.g. Windows 10, 1822]:
Windows 11 Pro, 22H2, 22621.1702

MSFT Build of OpenJDK Version:

OpenJDK Runtime Environment Microsoft-28056 (17.0.1+12) (build 17.0.1+12-LTS)

To Reproduce:
I am not sure how to reproduce this, as it seems to be a weird bug only happening on my pc.

  1. Launch minecraft
    Expected behavior
    The game would run.

Screenshots, Logs etc
If applicable, add screenshots, logs to help explain your problem.

Additional context
I originally suspect that this is a minecraft issue, but I noticed that in one of my crash reports the problematic frame is "V [jvm.dll+0x583f1b]". I also tried other jdks i can find (OpenJDK 17, OpenJDK 21, Oracle 17, BellSoft 17, BellSoft 21). The exceptions are mainly EXCEPTION_ACCESS_VIOLATION, EXCEPTION_ILLEGAL_INSTRUCTION, and EXCEPTION_PRIV_INSTRUCTION. It seems that mojang issue tracker is only accepting 1.20 and latest snapshot issues, so I decided to post this issue here.

below is the crash log, as it is too long to be included here
hs_err_pid13620.log

Thank you for the report!
It looks like you are reporting that the game Minecraft crashed for you. Please try the following:

  • Update your graphics drivers, see this Minecraft Help Center article, section "Update your Video Card Drivers";
    often Minecraft crashes are caused by outdated graphics drivers
  • In case you are using mods, try disabling them one by one until you find the mod causing the crash, then report the crash to the mod author
  • If you are using a third-party launcher, try the official launcher instead

If none of the above helped, and you are still experiencing the crash with the official launcher and without any mods installed, please submit this issue over at the Mojang bug tracker. Please search for existing reports first; in case you do not find any, create a new report and let us know about the issue number here (e.g. MC-123456).
The Mojang team will take the first look. If an OpenJDK bug is identified, the Mojang team will contact the Microsoft Build of OpenJDK team to address the issue.