JIRA Crashes due to Segmentation Fault in Java 8 JVM

Still need help?

The Atlassian Community is here for you.

Ask the community

Problem

The JIRA process crashes with a segmentation fault. The JVM version is either 1.8.0_25 or 1.8.0_31.

The following appears in the atlassian-jira.log:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x################, pid=#####, tid=###############
#
# JRE version: Java(TM) SE Runtime Environment (8.0_25-b17) (build 1.8.0_25-b17)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0x858a05]  LoadKlassNode::make(PhaseGVN&, Node*, Node*, TypePtr const*, TypeKlassPtr const*)+0x45
#
# Failed to write core dump. 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:
# /tmp/hs_err_pid#####.log
#
# Compiler replay data is saved as:
# /tmp/replay_pid#####.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
#

Cause

This is caused by a bug in the JVM documented at https://bugs.openjdk.java.net/browse/JDK-8061428 that affects versions 1.8.0_25 and 1.8.0_31. This has been fixed in version 1.8.0_40.

Resolution

Last modified on Mar 30, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.