-
Bug
-
Resolution: Fixed
-
P4
-
6
-
mustang
-
x86, sparc
-
solaris_9, windows_xp
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2120396 | 5.0 | Daniel Daugherty | P4 | Resolved | Fixed | rc |
JDK-2124370 | 1.4.2_10 | J. Duke | P3 | Resolved | Fixed | b01 |
Name: tb29552 Date: 01/05/2004
FULL PRODUCT VERSION :
java version "1.4.2_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_02-b03)
Java HotSpot(TM) Client VM (build 1.4.2_02-b03, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Windows NT 5.01
A DESCRIPTION OF THE PROBLEM :
JVM never completes startup when JVMPI is enabled and it is being debugged.
If I was a betting man, I'd say there was some kind of deadlock occurring, because it just hangs, shortly after JVM_OnLoad.
This is a regression, 1.4.2_01 and early works fine.
FYI, problem also occurs with 1.5.0-b26
You wouldn't think it would be much of a problem, but I need to collect coverage data while debugging my program & that requires JVMPI.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
This occurs ONLY on 1.4.2_02, 1.4.2_01 and 1.4.2_00 work fine.
Steps:
[f:\jdks\jdk1.4.2\demo\jfc\notepad] jdb
Initializing jdb ...
> run -Xrunhprof -jar Notepad.jar
run -Xrunhprof -jar Notepad.jar
[ VM hangs at this point ]
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
When it works (for 1.4.2_01, for example), the notepad window opens. :)
ACTUAL -
JVM hangs at 0% CPU until control-c is pressed.
REPRODUCIBILITY :
This bug can be reproduced always.
(Review ID: 229515)
======================================================================
- backported by
-
JDK-2124370 deadlock at VM startup when JVMPI / JDWP both enabled
- Resolved
-
JDK-2120396 deadlock at VM startup when JVMPI / JDWP both enabled
- Resolved
- relates to
-
JDK-4852569 OBJ_ALLOC event deadlock between VMThread and Finalizer thread
- Resolved