[MC-307416] The game crashes shortly after startup with the Vulkan rendering backend when using a third-party Java runtime environment

Game crashes after 15 seconds of just being on the title screen.

Attached are (unwrapped) vanilla game logs, and mprof (memory_profiler) report for memory usage and the csv results of a custom wrapper script to measure vram usage every 100ms.

Environment

OS: Arch Linux x86_64; Kernel: Linux 6.19.11-1-cachyos; Uptime: 3 hours, 38 mins; Packages: 2198 (pacman), 12 (flatpak-system), 7 (flatpak-user); Shell: fish 4.6.0; Display (AG276QZD2): 2560x1440 in 27", 240 Hz [External]; WM: Hyprland 0.54.3 (Wayland); CPU: AMD Ryzen 7 9800X3D (16) @ 5.27 GHz; GPU: AMD Radeon RX 9070 XT [Discrete]; Memory: 6.58 GiB / 62.37 GiB (11%); Swap: Disabled; Disk ✔ : 1.20 TiB / 1.67 TiB (72%) - ext4; Locale: en_GB.UTF-8; mesa 2:26.0.4-2; mesa-utils 9.0.0-7.1; vulkan-mesa-implicit-layers 2:26.0.4-2; vulkan-radeon 2:26.0.4-2

Linked issues

is duplicated by 1

MC-307307 26.2 Snapshot 1 - Vulkan Renderer crashes with exit code 11 (Segmentation Fault) on Linux using Mesa/RADV (OpenGL works fine) Resolved

Attachments

launcher_log.txt

log.txt

mprofile_20260409172932.dat

vram_usage_76251.csv

Comments 7

Automation for Jira 2026-04-09T16:33:32Z

Thank you for helping us improve Minecraft! We saved your files:

[media][media][media]

MrMuskle 2026-04-09T17:45:29Z

Please test if this issue also occurs in a vanilla environment, i.e., when using the official Minecraft Launcher.

If it does, please attach the full launcher log from when this issue occurred. You can find it in the .minecraft directory, named launcher_log.txt.

_{This ticket is being temporarily resolved as}_{Awaiting Response}_{. Once the requested information has been delivered, the ticket will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Victor Rijnoveanu 2026-04-09T17:58:21Z

Upon further research it turns out it was the openjdk 25 build on my system. The provided java runtime has no issues. My apologies. Here is the log regardless.

[media]

Zhai Can 2026-04-12T15:49:03Z

Could you try adding JVM option -XX:CompilerThreadStackSize=2048?

Arisa Bot 2026-04-12T15:56:40Z

Your comment(s) 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

Victor Rijnoveanu 2026-05-19T18:35:30Z

Zhai Can, yes that did fix my issue. Sorry for the very late reply I must have missed the email. It runs successfully on my system OpenJDK rather than having to use the Temurin JDK (which I just realized I compiled with march native and mtune native)

Zhai Can 2026-05-20T00:06:05Z

Happy to know that! I’ve reported this in openjdk’s mailing list and they filed the bug: (issue id) JDK-8382195, fyi