-
Bug
-
Resolution: Fixed
-
P2
-
6
-
b56
-
generic
-
generic
FULL PRODUCT VERSION :
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b47)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b47, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Dual processor - don't know if it matters.
A DESCRIPTION OF THE PROBLEM :
ThreadReference.isAtBreakpoint() and ThreadReference.ownedMonitors() are sometimes
very slow, taking as much as half a second to complete. This is not always the case,
but seems to happen immediately after a breakpoint, for example. We always call these
while the vm is suspended. The problem did not happen in Java 1.5 or any previous
versions. Our debugger continuously displays the status and monitors for each thread,
and because of this it is basically unusable under Java 1.6.
REPRODUCIBILITY :
This bug can be reproduced often.
CUSTOMER SUBMITTED WORKAROUND :
Don't call these methods.
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b47)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b47, mixed mode, sharing)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]
EXTRA RELEVANT SYSTEM CONFIGURATION :
Dual processor - don't know if it matters.
A DESCRIPTION OF THE PROBLEM :
ThreadReference.isAtBreakpoint() and ThreadReference.ownedMonitors() are sometimes
very slow, taking as much as half a second to complete. This is not always the case,
but seems to happen immediately after a breakpoint, for example. We always call these
while the vm is suspended. The problem did not happen in Java 1.5 or any previous
versions. Our debugger continuously displays the status and monitors for each thread,
and because of this it is basically unusable under Java 1.6.
REPRODUCIBILITY :
This bug can be reproduced often.
CUSTOMER SUBMITTED WORKAROUND :
Don't call these methods.
- relates to
-
JDK-6230707 Need to be able to get the location at which a monitor was acquired
-
- Resolved
-