OS version: MS Windows XP Professional and 2003 Server
Product Name: Sun JDK 1.4.2_08 and Sun JDK 1.4.2_09
Product version: Sun JDK 1.4.2_08 () and Sun JDK 1.4.2_09 (build 1.4.2_09-b05)
Short description: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at JVM.DLL batch process
Full problem description: This error happens each 3 or 4 retries. It doesn?t happen in all runs, but it crashes the VM. Follows the Stack and Dupm information:
Stack: [0x3c2e0000,0x3c320000), sp=0x3c31fbd4, free space=254k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [jvm.dll+0xa5b3e] V [jvm.dll+0x5cc1b] V [jvm.dll+0x5cd11] V [jvm.dll+0xd0a81]
RROR MESSAGES/STACK TRACES THAT OCCUR :
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x080a5b3e, pid=976, tid=2300 # # Java VM: Java HotSpot(TM) Client VM (1.4.2_09-b05 mixed mode) # Problematic frame:
# V [jvm.dll+0xa5b3e].
------------------------------------------------------------------------------------------
We just got new information that the problem seems to be caused by the reference to a dynamically generated class that has already been destroyed by GC.
Product Name: Sun JDK 1.4.2_08 and Sun JDK 1.4.2_09
Product version: Sun JDK 1.4.2_08 () and Sun JDK 1.4.2_09 (build 1.4.2_09-b05)
Short description: EXCEPTION_ACCESS_VIOLATION (0xc0000005) at JVM.DLL batch process
Full problem description: This error happens each 3 or 4 retries. It doesn?t happen in all runs, but it crashes the VM. Follows the Stack and Dupm information:
Stack: [0x3c2e0000,0x3c320000), sp=0x3c31fbd4, free space=254k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) V [jvm.dll+0xa5b3e] V [jvm.dll+0x5cc1b] V [jvm.dll+0x5cd11] V [jvm.dll+0xd0a81]
RROR MESSAGES/STACK TRACES THAT OCCUR :
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x080a5b3e, pid=976, tid=2300 # # Java VM: Java HotSpot(TM) Client VM (1.4.2_09-b05 mixed mode) # Problematic frame:
# V [jvm.dll+0xa5b3e].
------------------------------------------------------------------------------------------
We just got new information that the problem seems to be caused by the reference to a dynamically generated class that has already been destroyed by GC.
- relates to
-
JDK-6409422 EXCEPTION_ACCESS_VIOLATION coming to a safepoint?
-
- Closed
-