Bug ID: JDK-6484168 jvm hotspot compiler crashing on NotifyEvent.equals()

Type: Bug
Component: hotspot
Sub-Component: compiler
Affected Version: 5.0u5

Priority: P3
Status: Closed
Resolution: Cannot Reproduce
OS: windows_2003
CPU: x86

Submitted: 2006-10-19
Updated: 2011-02-16
Resolved: 2006-10-23

Customer gets hotspot error below when running his application.
JVM under JBOSS is crashing.
Customer would like some indication of which release this might get fixed in.

Also occurs with 5.0_10 he says.

If he excludes the method in question, then it runs ok.

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d8c17e4, pid=504, tid=1180
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_06-b05 mixed mode)
# Problematic frame:
# V  [jvm.dll+0x417e4]
#

---------------  T H R E A D  ---------------

Current thread (0x53399250):  JavaThread "CompilerThread1" daemon [_thread_in_native, id=1180]

siginfo: ExceptionCode=0xc0000005, reading address 0x00000000

Registers:
EAX=0x5669320c, EBX=0x00ac5c20, ECX=0x00000000, EDX=0x56693338
ESP=0x53c7f290, EBP=0x53c7f2c0, ESI=0x00000000, EDI=0x00000045
EIP=0x6d8c17e4, EFLAGS=0x00010202

Top of Stack: (sp=0x53c7f290)
0x53c7f290:   56693338 56697d78 6db71868 56697d78
0x53c7f2a0:   56693338 00000000 563355e8 00000000
0x53c7f2b0:   00000045 00000010 00000002 56693348
0x53c7f2c0:   ffffffff 6d8c1530 56697d78 0000004b
0x53c7f2d0:   53c7f588 56691270 56693338 00000002
0x53c7f2e0:   56ab72cc 00000002 0000000c ffffffff
0x53c7f2f0:   6d8c1d2a 53c7f588 0000004b 56690988
0x53c7f300:   6db77030 00000008 00000037 53c7f8d4

Instructions: (pc=0x6d8c17e4)
0x6d8c17d4:   00 00 8b 55 e0 8b 42 04 8b 34 b8 8b ce 89 75 e4
0x6d8c17e4:   8b 16 ff 92 c0 00 00 00 8b d8 8b cb e8 3b 64 25


Stack: [0x53b80000,0x53c80000),  sp=0x53c7f290,  free space=1020k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [jvm.dll+0x417e4]


Current CompileTask:
opto:2588      com.kronos.wfc.platform.notification.framework.NotifyEvent.equals(Ljava/lang/Object;)Z (127 bytes)


---------------  P R O C E S S  ---------------

Java Threads: ( => current thread )
  0x55966310 JavaThread "RMI TCP Connection(2665)-10.1.10.173" daemon [_thread_in_native, id=4932]
  0x54b23b30 JavaThread "RMI TCP Connection(2664)-10.1.10.171" daemon [_thread_in_native, id=2360]
  0x54cf6dc8 JavaThread "RMI TCP Connection(2663)-10.1.10.163" daemon [_thread_in_native, id=4564]
  0x568b7008 JavaThread "Thread-115" [_thread_blocked, id=5856]
  0x54d77d10 JavaThread "RMI TCP Connection(2660)-10.1.10.170" daemon [_thread_in_native, id=4852]
  0x56c9b5c8 JavaThread "RMI ConnectionExpiration-[10.1.10.162:1295]" daemon [_thread_blocked, id=5332]
  0x56126b90 JavaThread "RMI TCP Connection(2651)-10.1.10.167" daemon [_thread_in_native, id=5512]
  0x5449ae40 JavaThread "RMI ConnectionExpiration-[10.1.10.158:1293]" daemon [_thread_blocked, id=3556]

<snipped>

3 logs and the customer routine NotifyEvent.java that calls the function in question are located in  /net/cores/cores/65161763

EVALUATION Closing as not-reproducible. Will reconsider if customer sees crash with up-to-date VM.

23-10-2006

EVALUATION Customer is ok to close the case he opened for this bug. He agreed he would send in log files if he saw it occur in 5.0_08 or above, but for now we don't need to do anything. He is not certain he saw it in a later release then 5.0_06 and may have been mistaken when he opened the case.

23-10-2006