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.
I used "Find Usages" to find some (>500) method calls in our >1700 sources and then navigated to the places in the code by clicking on the nodes of the "Find Usages" result tree. I always delete the corresponding line. After doing so for a while, especially when working through multiple occurences in large files (>2000 lines), NB stars consuming 100% CPU and becomes unresponsive. If I leave it alone for a while, it goes back to 0% CPU. But this behavior is unacceptable. I already switched off background compilation (set delay to 0) and code folding to rule those out. I also have plenty of heap (300 MB, 150 MB used) and I tried default GC and concurrent/parallel GC. Using current q-build with JDK 1.4.2_05. The machine is an AMD XP2000+ with 1 GB RAM. Attaching one text file with 2 thread dumps from the situation.
Created attachment 16171 [details] Thread dumps.
According to the attached thread dumps, it seems to be a problem of javacore. Reassigning for further evaluation.
Should be fixed in trunk. Redundant invocation of refreshAnnotations() fixed. Checking in JavaEditor.java; /cvs/java/src/org/netbeans/modules/java/JavaEditor.java,v <-- JavaEditor.java new revision: 1.164; previous revision: 1.163 done Please reopen with additional thread-dump(s) if you can still reproduce it.
Apparantly, it still happens while editing large source files in NB 20040729. Attaching new ThreadDump.
Created attachment 16724 [details] New ThreadDump.
Created attachment 16774 [details] Another ThreadDump.
Please try the latest dev build. There is a lot of running parser instances in your thread dumps. This was fixed as issue #46688.
Reorganization of java component