我正在使用STAF v3.4.24在Sles12sp2上进行重新启动测试,一段时间后出现此错误:
I am doing reboot tests on Sles12sp2 using STAF v3.4.24 and after some time 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: # bugreport.java/bugreport/crash.jsp #我在Google上进行了搜索,大多数链接都是关于C库的. Java版本是8u121.在建议的位置未找到核心转储.
I have searched on Google and most of the links were about C library. Java version is 8u121. No core dump was found at the location proposed.
推荐答案在"com.sun.apache.xerces.internal.impl.xs.XMLSchemaValidator"的编译过程中,从C2编译器线程中崩溃的日志中: :handleStartElement,可能是严重的编译错误.没有适当的重制器,将很难在编译器中找出根本原因并立即修复.
From the logs you got crash in C2 compiler thread, during compilation of "com.sun.apache.xerces.internal.impl.xs.XMLSchemaValidator::handleStartElement" it could be sereous compilation bug. Without proper reporducer it will be difficult to identify the root cause in compiler and fix as wee.
作为替代方法,应使用-XX:CompileCommand = exclude排除此方法,com.sun.apache.xerces.internal.impl.xs.XMLSchemaValidator :: handleStartElement检查-XX的正确用法:CompileCommand =排除命令
As a work around you should exclude this method from compilation using -XX:CompileCommand=exclude, com.sun.apache.xerces.internal.impl.xs.XMLSchemaValidator::handleStartElement check the proper usage of the -XX:CompileCommand=exclude command
更多推荐
使用libjvm.so时出现Sigsegv Java致命错误
发布评论