This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 59541 - Evaluating hashmap of complex objects effectively blocks out the IDE
Summary: Evaluating hashmap of complex objects effectively blocks out the IDE
Status: VERIFIED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: PERFORMANCE
Depends on: 59945 60392
Blocks:
  Show dependency tree
 
Reported: 2005-06-02 10:39 UTC by Antonin Nebuzelsky
Modified: 2005-10-04 12:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread Dump (22.25 KB, text/plain)
2005-06-02 10:39 UTC, Antonin Nebuzelsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2005-06-02 10:39:07 UTC
If you debug an application and expand a complex hashmap in Local Variables view
or work with the hashmap in Watches, the IDE goes gray for a long time. It may
take unbearably long time (minutes) and the user has to kill the IDE.

See the attachment with thread dump. There is something awkward being done in
AWT thread...
Comment 1 Antonin Nebuzelsky 2005-06-02 10:39:49 UTC
Created attachment 22446 [details]
Thread Dump
Comment 2 Martin Entlicher 2005-06-02 10:50:34 UTC
Are you sure you tested 4.1? According to the thread dump it looks like 4.2. Can
you please provide the build number? Thanks.
Comment 3 Antonin Nebuzelsky 2005-06-02 10:53:50 UTC
You are right. I was reproducing the problem in 4.2. But the user reported the
problem against 4.1, so I set the Version to 4.1...
Comment 4 Martin Entlicher 2005-06-02 11:03:00 UTC
There could be similar problem in 4.1, but you would have to provide thread dump
from 4.1.
Things has changed a lot in this area between 4.1 and 4.2. So it's definitely
better to have the 4.2 thread dump.
Comment 5 Martin Entlicher 2005-06-22 15:13:13 UTC
Issue #59945 is fixed, but it did not fixed this performance problem.

There is a problem, that the Map is visualized like an array of key-value pairs.
But that array is not truncated in any way, nor nested like ordinary arrays.
Therefore a lot of nodes are created, which have no practical reason anyway. The
visualization should be improved.

Another problem is caused by using evaluatedNodes and evaluationQueue
collections. As the number of nodes is growing, these collections gets bigger
and it takes more and more time to process them. This approach was used as a
workaround so that we did not have to make API changes. But if that info is
associated directly with the Variable, it would scale better.
Comment 6 Martin Entlicher 2005-09-02 17:44:10 UTC
After issue #60392 was fixed, this is finally fixed.
Comment 7 Antonin Nebuzelsky 2005-09-13 13:37:32 UTC
build 200509112000

I still see the problem.
Comment 8 Martin Entlicher 2005-09-21 17:07:16 UTC
The original problem was fixed. You hit issue #64852.
Comment 9 Antonin Nebuzelsky 2005-10-04 12:33:38 UTC
V