The game will unpredictably crash. This has happened during the splash screen as well as during actual gameplay.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f1955bb7f26, pid=1901, tid=0x00007f19573cf700
#
# JRE version: OpenJDK Runtime Environment (8.0_212-b01) (build 1.8.0_212-b01)
# Java VM: OpenJDK 64-Bit Server VM (25.212-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libjemalloc.so+0x33f26]
#
# Core dump written. Default location: /home/cole/.minecraft/core or core.1901
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Related issues
is duplicated by
Attachments
Comments


I root-caused this to a change in jemalloc version. Prerelease 3 downgraded to LWJGL 3.1.6 (which includes jemalloc 5.1.0). Forcing the game to use lwjgl 3.2.1 (which includes jemalloc 5.2.0) solves the issue. See the details I wrote in MC-148505.

This happens on 1.14 pre-release 4 as well under Ubuntu 18.10, Oracle Java 8

I get this on 1.14 pre-release 4 on my arch linux desktop and my xubuntu 18.04 laptop. Using OpenJDK 8.

I can confirm for 1.14-pre5 to
[media]
Also confirming for 1.14 pre-5 on Fedora 29.

Ubuntu 19.10 also affected

Also confirming for 1.14 pre-5 on Debian
[media]Well I tried to upload the log...
File "hs_err_pid6878.log" was not uploaded
Jira could not attach the file as there was a missing token. Please try attaching the file again.

Can confirm for 1.14 Pre-3, 4 and 5 on Antergos.

@md_5 did you mean Ubuntu 18.10 or 19.04? I can confirm this on 19.04 as well.

Can confirm for 1.14 Pre-4 and Pre-5 on Linux Mint 18.3 'Sylvia' xfce 64-bit

I have confirmed that this issue occurs under Ubuntu 16.04, JRE 8 revision 201. Only started happening with 1.14 pre-release 5. Changing the JVM argument from -Xmx2G to -Xmx4G solved or worked around the issue with the client crashing during the splash screen loading phase.

Can confirm for Ubuntu 18.04 openjdk version 11.0.2 having issues 1.14 pre 3-5

I can confirm for Linux Mint 19 Tara with 1.14 pre 5.
I used the following 1.14test.json to use the newer lwjgl 3.2.1 as Sargun explains above: https://pastebin.com/XZkdw9Tw which is a workaround for the time being to allow me to play.
Steps for workaround:
1. Go to your minecraft folder (~/.minecraft)
2. Go in the versions folder
3. Copy '1.14 Pre-Release 5' folder to '1.14test'
4. Rename the .jar to '1.14test.jar' and the .json to '1.14test.json'
5. Paste from the pastebin link I gave above to replace the 1.14test.json file.
6. In Minecraft Launcher, go to 'Launch Options' and enable 'Advanced Settings'
7. Click Add new
8. Type in a name, such as '1.14 v5 patched' or 'Custom'
9. Under version, select 'snapshot 1.14test'
10. Click Save
11. Click News at the top to go back to main menu
12. Click the up arrow at the bottom to select the new launch option you just made.
13. Click Play, and you should be all set!

I have the same problem in 1.14 Pre-Release 5 (on Kubuntu 18.04 / 64bit).
Probably unrelated, since I can't reproduce it again, but it happened twice after a command like this (one time directly after, one time minutes later):
/summon minecraft:skeleton ~ ~ ~ {HandItems:[{id:"minecraft:barrier",Count:1b}]
}

Confirm on 14 pre 5.
Java:
openjdk version "1.8.0_201"
OpenJDK Runtime Environment (build 1.8.0_201-b09)
OpenJDK 64-Bit Server VM (build 25.201-b09, mixed mode)
System:
4.14.106-desktop-1.mga6 #1 SMP Thu Mar 14 18:01:29 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Confirmed 14pre5. Exact same as above. Changing to lwjgl 3.2.1 as above seems to have solved it temporarily.
openjdk 11.0.2 2019-01-15
OpenJDK Runtime Environment (build 11.0.2+9-Ubuntu-3ubuntu118.04.3)
OpenJDK 64-Bit Server VM (build 11.0.2+9-Ubuntu-3ubuntu118.04.3, mixed mode, sharing)
OS: Ubuntu 18.04.2 LTS x86_64
Kernel: 4.18.0-17-generic
Resolution: 1080x1920, 1920x1200
DE: GNOME 3.28.3
Terminal: terminator
CPU: Intel i7-6700K (8) @ 4.200GHz
GPU: NVIDIA GeForce GTX 980 Ti
Memory: 5353MiB / 15966MiB

In general, one of the workarounds we have employed locally is to use lwjgl-jemalloc 3.2.1 with the rest of lwjgl being at 3.1.6 on Linux - this hasn't caused any issues so far, and may be a consideration-worthy option.

Same problem on Manjaro with 1.14 Pre-Release 5.

Also confirmed on 1.14, seems like this wasn't fixed on macOS