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 get lots of exceptions and other errors in messages.log and NB consumes 100% CPU for a while, after clean + build project. For me, it looks as if the parser is scanning the .class files! We have the .class files in the source tree (build.classes.dir=${src.dir} in project.properties) and hide them with an appropriate pattern in system settings, which is perfectly legal, AFAIK. Using NB 20041005 with JDK 1.5.0. Attaching part of messages.log.
Created attachment 18153 [details] messages.log
Yes, this is reproducible.
Problem is in RepositoryUpdater. Martin will look at it.
NetBeans 20041012 just got hung up completely (had to kill it) after clean+build, I think because of the same problem. Attaching new messages.log with recursion stacktrace.
Created attachment 18321 [details] Recursion stacktrace.
This problem exposes a bug in RepositoryUpdater which behaves inconsistently with respect to FileScanner.
Btw. the recursion is fixed in the current build. Now I am going to fix the RepositoryUpdater.
Fixed. Checking in src/org/netbeans/modules/javacore/scanning/ClassUpdater.java; /cvs/java/javacore/src/org/netbeans/modules/javacore/scanning/ClassUpdater.java,v <-- ClassUpdater.java new revision: 1.9; previous revision: 1.8 done Processing log script arguments... More commits to come... Checking in src/org/netbeans/modules/javacore/RepositoryUpdater.java; /cvs/java/javacore/src/org/netbeans/modules/javacore/RepositoryUpdater.java,v <-- RepositoryUpdater.java new revision: 1.22; previous revision: 1.21 done
This seems to be OK now in build 20041017. I deleted the mdrstorage folder before testing, to be sure, everything would be rebuild. But I got 2 informational exceptions in the log during or after classpath scanning regarding a source, that was open in the editor at last shutdown. Are these a problem? Attaching messages.log.
Created attachment 18344 [details] Informational exceptions.
I am not sure. We should investigate it, so I am reopening the bug, but lowering the priority since these exceptions are not fatal. I will add some debugging output to the code so that you could provide more information when this happens again.
Debug info added. Checking in src/org/netbeans/modules/javacore/jmiimpl/javamodel/ResourceImpl.java; /cvs/java/javacore/src/org/netbeans/modules/javacore/jmiimpl/javamodel/ResourceImpl.java,v <-- ResourceImpl.java new revision: 1.36; previous revision: 1.35 done
*** Issue 50377 has been marked as a duplicate of this issue. ***
OK, we finally managed to track down the "Info is null..." problem - it was caused by a wrong synchronization and is now fixed. Checking in src/org/netbeans/modules/javacore/jmiimpl/javamodel/ResourceImpl.java; /cvs/java/javacore/src/org/netbeans/modules/javacore/jmiimpl/javamodel/ResourceImpl.java,v <-- ResourceImpl.java new revision: 1.41; previous revision: 1.40 done
Reorganization of java component