mojira.dev
MC-268115

Random segmentation faults during play

Randomly, often when left alone on the pause screen, Minecraft will randomly experience a segmentation fault. I have experienced this issue with any version from 1.18.2 to 1.20.4, however, I have not played 1.17 enough to experience this. I have had this happen with multiple versions of Java 17, OpenJDK and Corretto. The segmentation faults tend to have a similar segmentation fault dump log, and they appear to cause a desync between player data and world data, causing item/block duplication and loss. This happens frequently enough to be disruptive, although not enough to make the game unplayable. Previous memory tests using Memtest86+ passed, so it may not be a hardware issue. Note that I ran this using a third-party launcher application (Prism Launcher), but i feel it was unlikely to affect this. I have been able to reproduce this by simply leaving the game on the pause screen for an extended period of time. Note that the segmentation fault log i have provided happened during world creation, which is rare for me (However, this may simply be caused by the fact that I do not create many worlds).

[^hs_err_pid580.log]

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f0f654988a9, pid=580, tid=642
#
# JRE version: OpenJDK Runtime Environment 21.9 (17.0.9+7) (build 17.0.9+7)
# Java VM: OpenJDK 64-Bit Server VM 21.9 (17.0.9+7, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# J 16163 c2 jb.j(Ljb;)D (20 bytes) @ 0x00007f0f654988a9 [0x00007f0f65498820+0x0000000000000089]

Attachments

Comments 3

The item. loss/duplication is a duplicate of MC-63; the segmentation fault seems like a technical support issue, for which contact Mojang Support.

Please check whether this affects the vanilla launcher. It's possible that PrismLauncher uses some corrupted library for example.

Also I've noticed that the PrismLauncher profile is called "1.20.1" - is that the version you're trying to play? If so, please try 1.20.4 and whether the issue happens there as well.

This issue is being temporarily resolved as Awaiting Response. Once the requested information has been delivered, the report 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

The instance is called 1.20.1 because it was originally 1.20.1 but it was later updated to 1.20.4. Also, I have not yet been able to get the version on the Minecraft Launcher to crash, but this may be some other unsatisfied requirement i do not know about.

KSPAtlas

(Unassigned)

Unconfirmed

(Unassigned)

jvm-crash

1.20.4

Retrieved