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.
OS: Linux 2.6 WM: KDE 3.3 JAVA: jdk1.5.0-b64 Netbeans: 4.0 beta 2 This is Related to BUG #50429 Please Read that before using this: If in the Library Manage you apply the steps used in BUG #50429 except with respect to the Source Tab, then: 1. Netbeans generates an exception in the Scanning Project Classpaths Dialog (on startup) Note: The window appears and then is automatically closed (i.e. it flashes on the screen). 2. If you open a java file from the project Tab, the Scanning Project Classpaths Dialog pops up and generates the exception. 3. If you close the exception, it automatically restart the Scanning Project Classpaths Dialog and the exception (the only solution is to do something like xkill and kill Netbeans). Workaround: If you don't do step 3 and go directly the Library Manager to change the folder directory you can avoid the recurring exception.
Created attachment 18298 [details] Log File
Reassigning for evaluation.
The exceptions comming from b-tree were fixed. The other exceptions are a consequence of a bug in the java project. Maybe it is also fixed. Anyway, I guess the javacore scanning could be made more robust to not get into an infinite loop in such case.
I wasn't able to reproduce this (neither already closed issue 50429 or this one). If otherwise, feel free to reopen, thanks.