libjvm.so中的SIGSEGV Java致命错误

我正在使用STAF v3.4.24对Sles12sp2进行重启测试,一段时间后我收到此错误：

# 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 @R_881_4045@ion 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
#

我在谷歌搜索过,大部分链接都是关于C库的. Java版本是8u121.在拟议的地点没有发现核心转储.

解决方法

从日志中你在C2编译器线程中崩溃,在编译“com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator :: handleStartElement”期间,它可能是一个严重的编译错误.如果没有适当的reporducer,很难在编译器中找出根本原因并将其修复为wee.

作为解决方法,您应该使用-XX从编译中排除此方法：CompileCommand = exclude,com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator :: handleStartElement检查-XX的正确用法：CompileCommand =排除命令