The following crash was repeatedly reported for JRE 6 Update 13
64-bit VM on Windows Server 2003 (AMD64):
hs_err_pid date elapsed time
--------------------------------------------------------------
hs_err_pid1364.log: Fri Oct 09 17:47:45 2009 475347 seconds
hs_err_pid3740.log: Sun Oct 18 21:55:58 2009 1268698 seconds
hs_err_pid4264.log: Mon Oct 26 18:03:55 2009 1945152 seconds
hs_err_pid5212.log: Tue Nov 03 09:58:40 2009 1343005 seconds
hs_err_pid5148.log: Thu Dec 17 14:45:15 2009 2796181 seconds
hs_err_pid5072.log: Thu Jan 14 18:20:16 2010 382901 seconds
hs_err_pid3512.log: Mon Jan 18 12:53:29 2010 708899 seconds
The crash obviously occurs in always the same way, as the stack trace
appears identical from hs_err_pid.log files for all 6 incidents:
Stack: [0x0000000013a60000,0x0000000013b60000], sp=0x0000000013b5f720, free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x354a88]
?follow_stack@PSParallelCompact@@CAXPEAVParCompactionManager@@@Z+0x38
From dump file corresponding to hs_err_pid3512.log the following
stack trace was retrieved:
0:006> k
Child-SP RetAddr Call Site
00000000`13b5e4d8 00000000`77d704ff ntdll!NtWaitForSingleObject+0xa
00000000`13b5e4e0 00000000`6dbac2e6 kernel32!WaitForSingleObjectEx+0x130
00000000`13b5e580 00000000`6dca7cc1 jvm!os::fork_and_exec+0x86
00000000`13b5e670 00000000`6dbae91f jvm!VMError::report_and_die+0x771
00000000`13b5e740 00000000`6dbaf0ef jvm!topLevelExceptionFilter+0x35f
00000000`13b5e7e0 00000000`77ee6593 jvm!`java_start'::`1'::filt$0+0xf
00000000`13b5e810 00000000`77ee459d ntdll!_C_specific_handler+0x9b
00000000`13b5e8a0 00000000`77ee60a7 ntdll!RtlpExecuteHandlerForException+0xd
00000000`13b5e8d0 00000000`77ef31ed ntdll!RtlDispatchException+0x1b4
00000000`13b5ef80 00000000`6dbe4a90 ntdll!KiUserExceptionDispatch+0x2d
00000000`13b5f520 00000000`6dbee19d jvm!PSParallelCompact::follow_stack+0x40
00000000`13b5f580 00000000`6dbeef42 jvm!ReferenceProcessor::process_discovered_reflist+0x27d
00000000`13b5f620 00000000`6dbe50d5 jvm!ReferenceProcessor::process_discovered_references+0xb2
00000000`13b5f6d0 00000000`6dbe6a10 jvm!PSParallelCompact::marking_phase+0x3d5
00000000`13b5f870 00000000`6dbe70af jvm!PSParallelCompact::invoke_no_policy+0x340
00000000`13b5fad0 00000000`6dca8725 jvm!PSParallelCompact::invoke+0x5f
00000000`13b5fb00 00000000`6dcab038 jvm!VM_ParallelGCSystemGC::doit+0xa5
00000000`13b5fb40 00000000`6dca9ed4 jvm!VM_Operation::evaluate+0x48
00000000`13b5fb70 00000000`6dcaa32a jvm!VMThread::evaluate_operation+0x74
00000000`13b5fbf0 00000000`6dcaa932 jvm!VMThread::loop+0x38a
00000000`13b5fca0 00000000`6dbaf099 jvm!VMThread::run+0x72
00000000`13b5fd00 000007ff`7fc411c4 jvm!java_start+0x89
00000000`13b5ff50 00000000`77d6b71a msvcrt!endthreadex+0xd4
00000000`13b5ff80 00000000`00000000 kernel32!BaseThreadStart+0x3a
0:006>
64-bit VM on Windows Server 2003 (AMD64):
hs_err_pid date elapsed time
--------------------------------------------------------------
hs_err_pid1364.log: Fri Oct 09 17:47:45 2009 475347 seconds
hs_err_pid3740.log: Sun Oct 18 21:55:58 2009 1268698 seconds
hs_err_pid4264.log: Mon Oct 26 18:03:55 2009 1945152 seconds
hs_err_pid5212.log: Tue Nov 03 09:58:40 2009 1343005 seconds
hs_err_pid5148.log: Thu Dec 17 14:45:15 2009 2796181 seconds
hs_err_pid5072.log: Thu Jan 14 18:20:16 2010 382901 seconds
hs_err_pid3512.log: Mon Jan 18 12:53:29 2010 708899 seconds
The crash obviously occurs in always the same way, as the stack trace
appears identical from hs_err_pid.log files for all 6 incidents:
Stack: [0x0000000013a60000,0x0000000013b60000], sp=0x0000000013b5f720, free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x354a88]
?follow_stack@PSParallelCompact@@CAXPEAVParCompactionManager@@@Z+0x38
From dump file corresponding to hs_err_pid3512.log the following
stack trace was retrieved:
0:006> k
Child-SP RetAddr Call Site
00000000`13b5e4d8 00000000`77d704ff ntdll!NtWaitForSingleObject+0xa
00000000`13b5e4e0 00000000`6dbac2e6 kernel32!WaitForSingleObjectEx+0x130
00000000`13b5e580 00000000`6dca7cc1 jvm!os::fork_and_exec+0x86
00000000`13b5e670 00000000`6dbae91f jvm!VMError::report_and_die+0x771
00000000`13b5e740 00000000`6dbaf0ef jvm!topLevelExceptionFilter+0x35f
00000000`13b5e7e0 00000000`77ee6593 jvm!`java_start'::`1'::filt$0+0xf
00000000`13b5e810 00000000`77ee459d ntdll!_C_specific_handler+0x9b
00000000`13b5e8a0 00000000`77ee60a7 ntdll!RtlpExecuteHandlerForException+0xd
00000000`13b5e8d0 00000000`77ef31ed ntdll!RtlDispatchException+0x1b4
00000000`13b5ef80 00000000`6dbe4a90 ntdll!KiUserExceptionDispatch+0x2d
00000000`13b5f520 00000000`6dbee19d jvm!PSParallelCompact::follow_stack+0x40
00000000`13b5f580 00000000`6dbeef42 jvm!ReferenceProcessor::process_discovered_reflist+0x27d
00000000`13b5f620 00000000`6dbe50d5 jvm!ReferenceProcessor::process_discovered_references+0xb2
00000000`13b5f6d0 00000000`6dbe6a10 jvm!PSParallelCompact::marking_phase+0x3d5
00000000`13b5f870 00000000`6dbe70af jvm!PSParallelCompact::invoke_no_policy+0x340
00000000`13b5fad0 00000000`6dca8725 jvm!PSParallelCompact::invoke+0x5f
00000000`13b5fb00 00000000`6dcab038 jvm!VM_ParallelGCSystemGC::doit+0xa5
00000000`13b5fb40 00000000`6dca9ed4 jvm!VM_Operation::evaluate+0x48
00000000`13b5fb70 00000000`6dcaa32a jvm!VMThread::evaluate_operation+0x74
00000000`13b5fbf0 00000000`6dcaa932 jvm!VMThread::loop+0x38a
00000000`13b5fca0 00000000`6dbaf099 jvm!VMThread::run+0x72
00000000`13b5fd00 000007ff`7fc411c4 jvm!java_start+0x89
00000000`13b5ff50 00000000`77d6b71a msvcrt!endthreadex+0xd4
00000000`13b5ff80 00000000`00000000 kernel32!BaseThreadStart+0x3a
0:006>