JIRA Crashes due to Segmentation Fault in Java 8 JVM
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
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:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
#
# 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
Upgrade Java to 1.8.0_40 or later, available for download at http://www.oracle.com/technetwork/java/javase/downloads/index.html.
For more information about how to switch the Java Virtual Machine used by JIRA, please refer to the links below:
Was this helpful?