Strong SIGSEGV Java error in libjvm.so
I am doing reboot tests on Sles12sp2 using STAF v3.4.24 and after a while I get this error:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f105e11e712, pid=6577, tid=0x00007f1027efe700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x63c712][thread 139707363079936 also had an error]
IndexSet::alloc_block_containing(unsigned int)+0x42
#
# Core dump written. Default location: /root/core or core.6577
#
# An error report file with more information is saved as:
# /root/hs_err_pid6577.log
[error occurred during error reporting , id 0xb]
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
I searched on google and most of the links were about C library. Java version is 8u121. No dump was found at the suggested location.
source to share
From the logs you came across on the C2 compiler thread, at compile time "com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator :: handleStartElement" it might be a gross compilation error. Without a proper reporter, it will be difficult to pinpoint the root cause in the compiler and fix it as a wee.
As a work around, you should exclude this method from compilation with -XX: CompileCommand = exclude, com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator :: handleStartElement check if using -XX is correct: CompileCommand = exclude command
source to share