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.
This issue was reported manually by dstrupl. It already has 1 duplicates Build: NetBeans IDE 6.8 Beta (Build 200910212001) VM: Java HotSpot(TM) Client VM, 10.0-b19, Java(TM) SE Runtime Environment, 1.6.0_05-b13 OS: Windows XP Maximum slowness yet reported was 16265 ms, average is 16265
Created attachment 102015 [details] nps snapshot
This one looks like a problem in Nodes. One call to setKeys takes 16s ... Platform team please evaluate.
First of all the update can be done outside of AWT. But still, can you see the amount of Dupl.getKey()? Looks like there is a lot of equal objects. Something like Collections.nCopy(key, 133)...
David probably forgot that there are modules which have no issues :-) Setting keys outside AWT is good idea (fixed). The number of duplicates is strange. It can happen only for toplevels (not a feature as the duplicates navigation does not work) for members they are filtered out. I'am not also filtering the top levels. As I don't believe that this is the case I've also added the logging. Fixed jet-main 872917c9714f
Integrated into 'main-golden', will be available in build *201010300000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/872917c9714f User: Tomas Zezula <tzezula@netbeans.org> Log: #190358:16s - java.navigation.ElementNode.updateRecursively()