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 Dev (Build 101209-7c45410ce536) VM: Java HotSpot(TM) 64-Bit Server VM, 17.1-b03, Java(TM) SE Runtime Environment, 1.6.0_22-b04 OS: Linux User Comments: dkonecny: restarted IDE Stacktrace: java.lang.NullPointerException at org.netbeans.modules.masterfs.filebasedfs.naming.NameRef.getIndex(NameRef.java:64) at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.cleanQueue(NamingFactory.java:313) at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.registerInstanceOfFileNaming(NamingFactory.java:179) at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.registerInstanceOfFileNaming(NamingFactory.java:143) at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.fromFile(NamingFactory.java:80) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.create(FileObjectFactory.java:417)
Created attachment 103770 [details] stacktrace
Created attachment 103798 [details] stacktrace closing project
Created attachment 103804 [details] stacktrace I closed all projects and restarted IDE. Error was thrown while opening IDE.
This bug already has 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=174817
Created attachment 103818 [details] stacktrace ok this is my last post going back to 6.9.1. reason: - 7.0beta has exceptions telling me to update because they are fixed - the actuial dev build does not work. As usual the problems come from scanning projects (building indexes or whatever). This has always been a *big* problem in netbeans. I will try the next beta, bye bye for now ;-)
Created attachment 103893 [details] stacktrace
Looks like it was introduced recently - all failures coming from NB build 101209.
Created attachment 103910 [details] stacktrace opening ide
This bug already has 10 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=174817
This bug is duplicate of bug 192941.