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.
Several last day builds throws this NPE related probably to one of my freeform projects: java.lang.NullPointerException at com.sun.org.apache.xerces.internal.dom.ParentNode.nodeListItem(ParentNode.java:814) at com.sun.org.apache.xerces.internal.dom.ParentNode.item(ParentNode.java:828) at org.netbeans.modules.project.ant.Util.findElement(Util.java:51) at org.netbeans.spi.project.support.ant.AntProjectHelper$10.run(AntProjectHelper.java:637) at org.openide.util.Mutex.readAccess(Mutex.java:181) at org.netbeans.spi.project.support.ant.AntProjectHelper.getConfigurationFragment(AntProjectHelper.java:634) at org.netbeans.spi.project.support.ant.AntProjectHelper.getPrimaryConfigurationData(AntProjectHelper.java:558) at org.netbeans.modules.ant.freeform.FreeformProject$Info.getDisplayName(FreeformProject.java:103) The freeform project of mine is there for quite some time, so if there were some changes in its format since, than that may be readon for the NPE. Attaching full log.
Created attachment 18579 [details] IDE log
I have seen this exception once or twice. I do not know what it means - the immediate error is inside Xerces code, but this could be triggered by something the IDE is doing wrong. If you can *reliably reproduce* the exception, somehow, on someone else's machine, I can probably fix it. Otherwise chances are slim. There have not been any changes in format since beta 2 (that is not allowed). Do you know exactly which build starting throwing the exception? When does the exception occur? When the project is opened? During startup only? Under some other conditions?
I will put in additional "thread armoring" which might prevent race conditions when accessing DOM. I don't know if such a race condition is the cause of this NPE however.
Unfortunately I am unable to reproduce the bug anymore. It used to happen on regular basis during IDE startup - just when project classpath was to be scanned. The situation lasted for about a week. Then It just magically disappeared when I have deleted netbean's log file - hard to find any connections.
OK, not much to do with it for now then.
x
*** This issue has been marked as a duplicate of 50198 ***
closed