JDK-4367945 : Debugging a swing application with HotSpot is very slow.
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmdi
  • Affected Version: 1.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2000-09-01
  • Updated: 2000-09-08
  • Resolved: 2000-09-08
Related Reports
Duplicate :  
JDK-4293376 - JDB is too slow on kestrel-beta
Description

Name: dc32491			Date: 09/01/2000


java version "1.3.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0-C)
Java HotSpot(TM) Client VM (build 1.3.0-C, mixed mode)


Debug an application containing some swing controls with the classic VM.  Now
debug the same application using the HotSpot VM.  Notice time difference in
swing components appearing and in stepping.  This slowdown gets progressively
higher if more swing components exist in the application.
(Review ID: 109211) 
======================================================================
Comments
EVALUATION daniel.daugherty@Eng 2000-09-06 I believe this problem has been resolved by the following bug fix: 4293376 4/5 JDB is too slow on kestrel-beta The fix for this bug was integrated in Kestrel Solaris. I think we need to get a Win32 VM to Helen to see if this issue is resolved. daniel.daugherty@Eng 2000-09-07 Customer has verified that this bug is fixed using a Win32 build of the Kestrel Solaris production bits. I'm closing this as a duplicate of 4293376.
07-09-2000