S
S
Sergey Bulatov2021-03-08 16:13:29
Java
Sergey Bulatov, 2021-03-08 16:13:29

Why is this error happening?

While running Bukkit server crashes with this error

[email protected]:/mnt/main/paper$ java -Xms2G -Xmx2G -jar paper114.jar[20:01:47 INFO]: [renardein: Set the time to 1000]
> #
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fdf76503b10, pid=6005, tid=6016
#
# JRE version: OpenJDK Runtime Environment (11.0.9.1+1) (build 11.0.9.1+1-post-Debian-1deb10u2)
# Java VM: OpenJDK 64-Bit Server VM (11.0.9.1+1-post-Debian-1deb10u2, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x793b10]
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /mnt/main/paper/hs_err_pid6005.log
#
# Compiler replay data is saved as:
# /mnt/main/paper/replay_pid6005.log
#
# If you would like to submit a bug report, please visit:
#   https://bugs.debian.org/openjdk-11
#
Аварийный останов
[email protected]:/mnt/main/paper$ java -Xms2G -Xmx2G -jar paper114.jar


Important note: This is how any jar crashes, therefore the problem is in java

. What is the problem and where to dig?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
Sergey Bulatov, 2021-03-09
@renardein

I answer my own question - although the crooked RAM timings passed Memtest, in reality they led to such nonsense

D
Dmitry Roo, 2021-03-08
@xez

In general, to the software manufacturer.
Well, you can still try another version of JRE (with 1.8, it might work).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question