一个JVM的错误让我遇到了:A fatal error has been detected by the Java Runtime Environment
来源:互联网 发布:网络电视cctv5 编辑:程序博客网 时间:2024/05/01 07:20
今天的dailybuild报了个错,第一次遇到,以前没遇到类似JVM的错误。
编译的错误生成生成的log名为hs_err_pid3692.log,保存在当前编译目录根目录下,至于这个hs_err_pidxxx.log文件怎么生成的呢??
错误问题
## A fatal error has been detected by the Java Runtime Environment:## target Java: com.qrd.plugin.feature_query (out/Myproject/target/common/obj/JAVA_LIBRARIES/com.qrd.plugin.feature_query_intermediates/classes)SIGSEGV (0xb) at pc=0x00002ae0a2bfb082, pid=3692, tid=47144387012352## JRE version: 6.0_24-b07# Java VM: Java HotSpot(TM) 64-Bit Server VM (19.1-b02 mixed mode linux-amd64 compressed oops)# Problematic frame:# V [libjvm.so+0x216082]## An error report file with more information is saved as:# /home/GoldenPlatform/Myproject/hs_err_pid3692.log## If you would like to submit a bug report, please visit:# http://java.sun.com/webapps/bugreport/crash.jsp#
编译的错误生成生成的log名为hs_err_pid3692.log,保存在当前编译目录根目录下,至于这个hs_err_pidxxx.log文件怎么生成的呢??
网上找了很多材料好像这种crash错误有很多种。目前只针对该问题,其他的后面分析。
问题分析
首先,编译在“target Java”生成的jar包 的时候出错了out\Myproject\target\product\Myproject\system\framework下的jar包生成不多,比往常少了。开始从hs_err_pid3692.log分析。
1. 提示的错误时pid3692是吧,那就查查这个PID3692是什么
2ae0a402c000-2ae0a402e000 rwxp 00008000 08:01 3677326 /opt/qcom/jdk5/jdk1.6.0_24/jre/lib/amd64/native_threads/libhpi.so2ae0a402e000-2ae0a402f000 rwxp 00000000 00:00 0 2ae0a402f000-2ae0a4037000 rwxs 00000000 08:01 681586 /tmp/hsperfdata_root/36922ae0a404a000-2ae0a4052000 r-xp 00000000 08:01 2883691 /lib/libnss_compat-2.11.1.so
2.hsperfdata_root又是个什么东西??
问题解决:
决定一边分析,一边重新让项目再编译一次,看这个问题是不是必现的,网上一查这个crash的错,好像很多。EXCEPTION_ACCESS_VIOLATION比较多,还有内存操作的。
问题没完全解决,只是重新编译一次就可以了。以为dailybuild服务器上编译是个项目,同一条代码分支,其他项目都没问题,所以不太觉得是编译环境的问题。但确实是重编就可以。http://bugreport.sun.com/bugreport/start_form.jsp上提bug还在等答复中
- 一个JVM的错误让我遇到了:A fatal error has been detected by the Java Runtime Environment
- JNI:一个典型的错误——A fatal error has been detected by the Java Runtime Environment
- jvm bug A fatal error has been detected by the Java Runtime Environment:
- Tomcat启动:A fatal error has been detected by the Java Runtime Environment(JVM)
- A fatal error has been detected by the Java Runtime Environment程序错误处理方法
- Tomcat启动:A fatal error has been detected by the Java Runtime Environment(JVM Crash分析及相关资料)
- Tomcat启动:A fatal error has been detected by the Java Runtime Environment(JVM Crash分析及相关资料)
- A fatal error has been detected by the Java Runtime Environment(JVM Crash分析及相关资料)
- Tomcat启动:A fatal error has been detected by the Java Runtime Environment(JVM Crash分析及相关资料)
- Fedora 17 下运行Kettle遇到"A fatal error has been detected by the Java Runtime Environment"
- JAVA VM bug :A fatal error has been detected by the Java Runtime Environment
- A fatal error has been detected by the Java Runtime Environment
- tomcat启动报错,A fatal error has been detected by the Java Runtime Environment:
- tomcat启动报错,A fatal error has been detected by the Java Runtime Environment
- JNA : A fatal error has been detected by the Java Runtime Environment
- Tomcat启动报A fatal error has been detected by the Java Runtime Environment
- 启动ADT bundle 时出错:A fatal error has been detected by the Java Runtime Environment:
- A fatal error has been detected by the Java Runtime Environment--排错
- Ubuntu12.04 搭建TFTP服务
- 串口转以太网模块--WIZ108SR 用户手册(一)
- 四大精刚
- 电脑重装
- 禁止IE8使用IE7的兼容模式
- 一个JVM的错误让我遇到了:A fatal error has been detected by the Java Runtime Environment
- JS, CSS 文件压缩与反压缩工具
- 【转载】Java 类型转换
- HTML --> META
- webdriver 如何处理时间控件
- C#动态操作DataTable(新增行、列、查询行、列等)
- 突破带宽瓶颈 3G视频监控市场前景广阔
- SQL连接方式(左连接、右连接、全连接)-转载
- Git系列之一 --- git remote