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.
Build: NetBeans IDE 6.8 Beta (Build 200910212001) VM: Java HotSpot(TM) Client VM, 1.5.0_19-137, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_19-b02-304 OS: Mac OS X, 10.5.7, i386 User Comments: jvaldes: scan projectss cesr42: On initially starting 6.8 beta for the first time, I closed the Start Page tab and got this error. GUEST: Occured upon first start of IDE. Did an import of my previous 6.5 settings. dnorton17: Opening Netbeans 6.8 beta for the first time after importing settings from 6.7.1 Stacktrace: java.lang.NullPointerException at org.netbeans.modules.project.ui.ProjectsRootNode$BadgingNode.replaceProject(ProjectsRootNode.java:515) at org.netbeans.modules.project.ui.ProjectsRootNode$BadgingNode.access$000(ProjectsRootNode.java:428) at org.netbeans.modules.project.ui.ProjectsRootNode.checkNoLazyNode(ProjectsRootNode.java:209) at org.netbeans.modules.project.ui.OpenProjectList$LoadOpenProjects.run(OpenProjectList.java:320) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1084)
Created attachment 90032 [details] stacktrace
This issue already has 6 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=159990
Build: NetBeans IDE 6.8 Beta (Build 200910212001) VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03 OS: Windows XP, 5.1, x86 User Comments: Thas show in my first use of the NetBeans IDE 6.8 Beta, I import the configs of the NetBeans IDE 6.7.1. Stacktrace: java.lang.NullPointerException at org.netbeans.modules.project.ui.ProjectsRootNode$BadgingNode.replaceProject(ProjectsRootNode.java:515) at org.netbeans.modules.project.ui.ProjectsRootNode$BadgingNode.access$000(ProjectsRootNode.java:428) at org.netbeans.modules.project.ui.ProjectsRootNode.checkNoLazyNode(ProjectsRootNode.java:209) at org.netbeans.modules.project.ui.OpenProjectList$LoadOpenProjects.run(OpenProjectList.java:320) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:602) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1084)
Created attachment 90035 [details] stacktrace
This issue already has 7 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=159990
This issue already has 12 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=159990
This issue already has 20 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=159990
So far not able to reproduce.
Added check for null. Original problem (unknown to me) is probably still there. http://hg.netbeans.org/core-main/rev/12d684c13733
Integrated into 'main-golden', will be available in build *200910280201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/12d684c13733 User: Milan Kubec <mkubec@netbeans.org> Log: #175347: check for null added
Reopening for further evaluation.
Jardo, please re-evalaute the issue. Thanks.
The NPE seems to be fixed by Milan. I am not sure what else I am supposed to do. I could write a test, but I do not really feel inspired by reproducing bug that cannot appear anymore. But if anyone wants, feel free to simulate the NPE. I can imagine it could happen when one restarts and some originally open project is no longer recognizable as project and thus ProjectManager.getDefault().findProject returns null.
Fixed in 12d684c13733
Reopening as was discussed with jtulach offline. Removing RANDOM, adding REGRESSION. This seems like much more severe problem than just a project which is not recognizable as a project after restart. So, catching this NPE only hides the problem which is still there. My assumption is based on the fact that this NPE is reported by many users of 6.8 Beta, and before beta there were no such reports. See http://statistics.netbeans.org/exceptions/detail.do?id=159990
Jarda will evaluate.
All last ten reports contain ERGO_PROJECT_OPEN soon after start. This seem to imply there is a problem during import of existing user director when starting with new version. Many of the reports open project type from enterprise cluster. The exception is thrown sooner than the enterprise modules are enabled however.
core-main#3e4b60867331