FULL PRODUCT VERSION :
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows XP [Version 5.1.2600]

A DESCRIPTION OF THE PROBLEM :
ThreadReference.isAtBreakpoint() and ThreadReference.ownedMonitors() are sometimes very slow for the DestroyJavaVM thread. In our debugger, we're seeing delays as long as two seconds on a 2GHz machine. The procedure below probably demonstrates the problem for jdb. This looks somewhat similar to 6311508.

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
jdb Test
stop at Test:3
run
resume
suspend
threads


EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Expect thread data to be displayed quickly.
ACTUAL -
Thread data is displayed quickly up until the DestroyJavaVM thread, for which there is a relatively long delay.

REPRODUCIBILITY :
This bug can be reproduced always.

---------- BEGIN SOURCE ----------
public class Test {
   public static void main(String[] args) {
      new javax.swing.JFrame().setVisible(true);
   }
}
---------- END SOURCE ----------

CUSTOMER SUBMITTED WORKAROUND :
Avoid calling isAtBreakpoint() or ownedMonitors() on the DestroyJavaVM thread.