-
JVM崩溃是什么原因5
请求大虾看看,小弟在此拜谢
报错信息:
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) Server VM (20.4-b02 mixed mode linux-x86 )
# Problematic frame:
# V [libjvm.so+0x3c2aee] instanceKlassKlass::oop_follow_contents(oopDesc*)+0x1de
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x09945400): VMThread [stack: 0x83ab5000,0x83b36000] [id=11392]
siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x040f94b0
Registers:
EAX=0x00000003, EBX=0x040f94b0, ECX=0x000000b8, EDX=0x0a6876f0
ESP=0x83b34bd0, EBP=0x83b34c18, ESI=0x8adf6ab8, EDI=0x00000001
EIP=0xb7691aee, EFLAGS=0x00010202, CR2=0x040f94b0
Top of Stack: (sp=0x83b34bd0)
0x83b34bd0: 893d4b78 00000002 83b34c18 00000003
0x83b34be0: 09945400 098c4be8 0a2e8098 0a2e84ac
0x83b34bf0: 0a2f008c 83b34de0 83b34c18 981adc1c
0x83b34c00: 8adf6c10 8adf6c10 00000003 893d4b78
0x83b34c10: 83b34c90 00000000 83b34c58 b784876d
0x83b34c20: 840b0158 8adf6ab0 893d4b78 893d4b78
0x83b34c30: b7aceb9c b7aceb60 b78914ab 83b34c80
0x83b34c40: 83b34c90 00000000 83b34cc8 b78f431f
Instructions: (pc=0xb7691aee)
0xb7691ace: d0 84 c0 0f 85 5c 09 00 00 57 57 53 68 40 9e ad
0xb7691ade: b7 e8 3c 20 da ff 83 c4 10 8b 5e 74 85 db 74 57
0xb7691aee: 8b 03 83 e0 03 83 f8 03 74 4d 8b 3b c7 45 c4 03
0xb7691afe: 00 00 00 8b 45 c4 89 03 80 3d 0d b0 ab b7 00 0f
Register to memory mapping:
EAX=0x00000003 is an unknown value
EBX=0x040f94b0 is an unknown value
ECX=0x000000b8 is an unknown value
EDX=0x0a6876f0 is an unknown value
ESP=0x83b34bd0 is an unknown value
EBP=0x83b34c18 is an unknown value
ESI=0x8adf6ab8 is an oop
{instance class}
- klass: {other class}
EDI=0x00000001 is an unknown value
Stack: [0x83ab5000,0x83b36000], sp=0x83b34bd0, free space=510k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x3c2aee] instanceKlassKlass::oop_follow_contents(oopDesc*)+0x1de
V [libjvm.so+0x57976d] MarkSweep::follow_stack()+0x3d
V [libjvm.so+0x625327] PSMarkSweep::mark_sweep_phase1(bool)+0xe7
V [libjvm.so+0x624427] PSMarkSweep::invoke_no_policy(bool)+0x3c7
V [libjvm.so+0x62402d] PSMarkSweep::invoke(bool)+0x7d
V [libjvm.so+0x7262ca] VM_ParallelGCSystemGC::doit()+0xda
V [libjvm.so+0x7345e6] VM_Operation::evaluate()+0x46
V [libjvm.so+0x733a93] VMThread::evaluate_operation(VM_Operation*)+0x83
V [libjvm.so+0x733d00] VMThread::loop()+0x190
V [libjvm.so+0x7337f0] VMThread::run()+0x80
V [libjvm.so+0x5e2b0e] java_start(Thread*)+0x14e
C [libpthread.so.0+0x5832] signed char+0x5832
VM_Operation (0x82cfec60): ParallelGCSystemGC, mode: safepoint, requested by thread 0x82ffd800
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x0a3c0000 JavaThread "http-bio-80-exec-247" daemon [_thread_blocked, id=15486, stack(0x7cbfe000,0x7ccff000)]
0x09c04800 JavaThread "http-bio-80-exec-246" daemon [_thread_blocked, id=15485, stack(0x7c0f8000,0x7c1f9000)]
0x09ce4000 JavaThread "http-bio-80-exec-245" daemon [_thread_blocked, id=15484, stack(0x7d1fa000,0x7d2fb000)]
0x09ace400 JavaThread "http-bio-80-exec-244" daemon [_thread_blocked, id=15483, stack(0x7cef7000,0x7cff8000)]
0x09cf1000 JavaThread "http-bio-80-exec-243" daemon [_thread_blocked, id=15482, stack(0x7c1f9000,0x7c2fa000)]
0x0a1eac00 JavaThread "http-bio-80-exec-242" daemon [_thread_blocked, id=15481, stack(0x7d3fc000,0x7d4fd000)]
0x09bd1000 JavaThread "http-bio-80-exec-233" daemon [_thread_blocked, id=14823, stack(0x7c5fd000,0x7c6fe000)]
0x09c05400 JavaThread "http-bio-80-exec-221" daemon [_thread_blocked, id=12099, stack(0x7c7ff000,0x7c900000)]
0x0a292c00 JavaThread "Timer-3" daemon [_thread_blocked, id=19682, stack(0x7cafd000,0x7cbfe000)]
0x81c57400 JavaThread "PageSavingThread-wicket" daemon [_thread_blocked, id=11488, stack(0x7bdf5000,0x7bef6000)]
0x821ed000 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=11483, stack(0x7c9fc000,0x7cafd000)]
0x0a432800 JavaThread "ajp-bio-8009-AsyncTimeout" daemon [_thread_blocked, id=11465, stack(0x7d4fd000,0x7d5fe000)]
0x09acf800 JavaThread "ajp-bio-8009-Acceptor-0" daemon [_thread_in_native, id=11464, stack(0x7d5fe000,0x7d6ff000)]
0x0a197400 JavaThread "http-bio-80-AsyncTimeout" daemon [_thread_blocked, id=11463, stack(0x7dfff000,0x7e100000)]
0x0a696400 JavaThread "http-bio-80-Acceptor-0" daemon [_thread_in_native, id=11462, stack(0x82afe000,0x82bff000)]
0x09a35000 JavaThread "ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon [_thread_blocked, id=11461, stack(0x7d6ff000,0x7d800000)]
0x8143b000 JavaThread "wcs111timerFactory" daemon [_thread_blocked, id=11445, stack(0x7e4fe000,0x7e5ff000)]
0x09e60000 JavaThread "GWC DiskQuota clean up thread-1" [_thread_blocked, id=11444, stack(0x7e7f6000,0x7e8f7000)]
0x0a106000 JavaThread "GWC DiskQuota Usage Stats Gathering Thread-1" [_thread_blocked, id=11443, stack(0x7e5ff000,0x7e700000)]
0x09e95c00 JavaThread "GWC DiskQuota Updates Gathering Thread-1" [_thread_blocked, id=11442, stack(0x7e8f7000,0x7e9f8000)]
0x81965c00 JavaThread "Thread-26" daemon [_thread_blocked, id=11441, stack(0x7e9f8000,0x7eaf9000)]
0x81e30800 JavaThread "GWC DiskQuota Store Writer-1" [_thread_blocked, id=11440, stack(0x7eaf9000,0x7ebfa000)]
0x81eb1800 JavaThread "Checkpointer" daemon [_thread_blocked, id=11439, stack(0x7ebfa000,0x7ecfb000)]
0x82d52400 JavaThread "Cleaner-1" daemon [_thread_blocked, id=11438, stack(0x7ecfb000,0x7edfc000)]
0x8343a800 JavaThread "INCompressor" daemon [_thread_blocked, id=11437, stack(0x802ff000,0x80400000)]
0x82777800 JavaThread "H2 Log Writer GWC_METASTORE" daemon [_thread_blocked, id=11436, stack(0x7edfc000,0x7eefd000)]
0x816ff400 JavaThread "H2 TCP Server (tcp://localhost:44722)" daemon [_thread_in_native, id=11434, stack(0x7eefd000,0x7effe000)]
0x828cac00 JavaThread "H2 File Lock Watchdog /opt/tomcat/temp/geowebcache/meta_jdbc_h2/gwc_metastore.lock.db" daemon [_thread_blocked, id=11433, stack(0x7effe000,0x7f0ff000)]
0x80407c00 JavaThread "GT authority factory disposer" daemon [_thread_blocked, id=11430, stack(0x800ff000,0x80200000)]
0x0a2a5c00 JavaThread "WeakCollectionCleaner" daemon [_thread_blocked, id=11427, stack(0x807ff000,0x80900000)]
0x82dc8400 JavaThread "Timer-2" daemon [_thread_blocked, id=11416, stack(0x810fe000,0x811ff000)]
0x81a1b000 JavaThread "Timer-1" daemon [_thread_blocked, id=11412, stack(0x811ff000,0x81300000)]
0x82dc1c00 JavaThread "Timer-0" daemon [_thread_blocked, id=11402, stack(0x81fff000,0x82100000)]
0x82ffd800 JavaThread "GC Daemon" daemon [_thread_blocked, id=11400, stack(0x82bff000,0x82d00000)]
0x83413400 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=11398, stack(0x8317d000,0x8327e000)]
0x83411c00 JavaThread "C2 CompilerThread1" daemon [_thread_blocked, id=11397, stack(0x8327e000,0x832ff000)]
0x8340fc00 JavaThread "C2 CompilerThread0" daemon [_thread_blocked, id=11396, stack(0x83513000,0x83594000)]
0x8340e400 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=11395, stack(0x832ff000,0x83400000)]
0x0994a800 JavaThread "Finalizer" daemon [_thread_blocked, id=11394, stack(0x838b3000,0x839b4000)]
0x09949000 JavaThread "Reference Handler" daemon [_thread_blocked, id=11393, stack(0x839b4000,0x83ab5000)]
0x098c9800 JavaThread "main" [_thread_in_native, id=11389, stack(0xb71ce000,0xb72cf000)]
Other Threads:
=>0x09945400 VMThread [stack: 0x83ab5000,0x83b36000] [id=11392]
0x83415800 WatcherThread [stack: 0x830fc000,0x8317d000] [id=11399]
VM state:at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x098c7dc0] Threads_lock - owner thread: 0x09945400
[0x098c81d0] Heap_lock - owner thread: 0x82ffd800
Heap
PSYoungGen total 91456K, used 546K [0xa9610000, 0xaf2b0000, 0xb40b0000)
eden space 90880K, 0% used [0xa9610000,0xa9610000,0xaeed0000)
from space 576K, 94% used [0xaeed0000,0xaef58a88,0xaef60000)
to space 1984K, 0% used [0xaf0c0000,0xaf0c0000,0xaf2b0000)
PSOldGen total 174784K, used 87610K [0x940b0000, 0x9eb60000, 0xa9610000)
object space 174784K, 50% used [0x940b0000,0x9963eaa0,0x9eb60000)
PSPermGen total 131072K, used 112465K [0x840b0000, 0x8c0b0000, 0x940b0000)
object space 131072K, 85% used [0x840b0000,0x8ae845b0,0x8c0b0000)
Code Cache [0xb417d000, 0xb4a65000, 0xb717d000)
total_blobs=2777 nmethods=2476 adapters=253 free_code_cache=41064320 largest_free_block=17408
..............................2012年2月21日 20:23
2个答案 按时间排序 按投票排序
-
我最近用eclipse调试时也JVM crash,后面猜测是eclipse按照目录下的配置文件或者workspace下面的配置文件出了问题,后面我重新解压eclipse,换掉workspace,再导入工程,然后调试,问题解决了,你可以尝试一下。日志文件的内容如下:
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6db7c3a1, pid=1460, tid=1520
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode)
# Problematic frame:
# V [jvm.dll+0x29c3a1]
#
--------------- T H R E A D ---------------
Current thread (0x449a3980): JavaThread "JDWP Transport Listener: dt_socket" daemon [_thread_in_vm, id=1520]
siginfo: ExceptionCode=0xc0000005, reading address 0x0000000c
....2012年2月22日 11:30
相关推荐
另一个重要的参数是`-XX:OnError`,它允许我们在JVM崩溃时执行自定义的命令,比如`pmap %p`用于显示进程的内存映射,或者`gcore %p; dbx - %p`用于生成核心转储并启动调试器。在Linux中,这些命令会在子进程中执行,...
理解JVM崩溃的原因和解决方法对于Java开发者来说至关重要。 在描述中提到了一个博客链接,虽然具体内容没有提供,但可以推测博主可能分享了关于JVM崩溃的案例分析或解决方案。通常,遇到JVM崩溃时,开发者会查看...
该项目是一款基于Java平台的JVM崩溃分析工具源码,包含22个文件,其中19个为Java源文件,1个JAR包文件,1个Markdown文件和1个XML文件。该工具专注于分析JVM崩溃原因并提供常见解决方案。
在"sigar1.6.4,jvm崩溃修复版"中,它特别针对JVM崩溃问题进行了优化和修复,提升了其在Java环境下的稳定性。 在JVM(Java Virtual Machine)中,崩溃可能由于多种原因,如内存溢出、线程死锁、非法指令或系统资源...
此为修复版本,下载后直接使用即可 版本号:1.6.4,大家去下载jar的时候别搞错了!
首先,我们需要了解JVM崩溃的常见原因。这可能包括内存溢出(Out of Memory Error)、线程死锁、非法指令、系统资源耗尽等。错误日志通常会提供以下几个关键部分的信息: 1. **头部信息**:包含崩溃时JVM的版本、...
在书上看到一个作者提出一个问题“怎样通过编写Java代码让Jvm崩溃”,我看了之后也不懂。带着问题查了一下,百度知道里面有这样一个答案: 1 package jvm; 2 3 public class Crash { 4 public static void main...
JVM监视能够帮助开发者识别内存泄漏、CPU过度使用、线程阻塞等问题,这些都可能导致应用性能下降甚至崩溃。通过实时监控,开发者可以快速定位问题,及时优化代码,提高应用的稳定性和效率。 ### jvm-mon的主要功能 ...
此外,提到内存溢出的问题,当应用程序需要的内存超过堆的最大值时,会导致JVM抛出内存溢出异常,使服务崩溃。通常建议将最大内存设置为物理内存的80%,以确保有足够的空间给其他系统进程。 垃圾回收的效率和频率与...
理解JVM的工作机制,对于提高程序性能、解决内存泄漏和避免系统崩溃至关重要。 JVM调优主要包括以下几个方面: 1. **内存管理**:JVM内存分为堆内存和栈内存,其中堆内存又分为新生代、老年代和永久代(Java 8后改...
Java的垃圾收集器(GC)负责自动管理内存,确保程序不会因内存泄漏而崩溃。为了监控和分析JVM的内存状况,开发者通常需要利用各种工具和配置选项。本文将深入探讨如何查看和分析JVM的内存状态,特别是通过输出GC日志...
"年轻代GC JVM crash"可能是因为在垃圾回收过程中遇到了严重问题,导致JVM崩溃。这可能是由于以下原因: 1. **内存溢出**:如果年轻代的空间不足以容纳新分配的对象,或者Survivor区无法容纳从Eden区晋升的对象,就...
JVM不仅仅是一个简单的解释器,它还包括垃圾收集器(GC)用于自动管理内存,确保程序不会因为内存泄漏或非法访问内存而导致崩溃。此外,JVM还提供了类装载器、运行时数据区、执行引擎以及一套丰富的类库,为开发者...
在JVM内存管理中,内存泄漏是一种常见的性能问题,可能导致应用运行缓慢,甚至崩溃。MAT通过解析JVM生成的hprof文件(内存快照),可以深入分析堆内存的各个部分,包括对象分配、存活状态、引用关系等,帮助定位问题...
它可以从core文件中提取出配置信息,这对于分析问题原因十分有价值。同样,jinfo只在Solaris和Linux的JDK版本中可用。 4. **jmap**: jmap可以提供内存映射的详细信息,包括堆大小、持久代大小等,这对于诊断内存...
合理配置JVM参数不仅可以显著提升应用程序的运行效率,还能避免因内存溢出等问题导致的系统崩溃。本文将深入探讨JVM参数配置的关键点,帮助读者掌握如何根据具体需求调整JVM,以达到最佳性能。 #### 二、JVM参数...
JVM性能调优是一项关键技术,旨在优化JVM的内存管理、垃圾收集、类加载等方面,以提升程序运行速度、减少内存占用并避免系统崩溃。本教程"JVM性能调优经典教程"由马士兵老师倾力讲解,旨在帮助Java开发者进阶,掌握...
这个文件对于开发者来说至关重要,因为它记录了JVM崩溃时的详细信息,包括堆栈跟踪、系统属性、线程信息以及可能的故障原因。 标题"JVM Crash,生成hs_err_pid.log文件"指的是Java虚拟机在运行过程中遇到了致命问题...