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.
dev build 200112030100 Annotations seem to be nice and broken in this release. Below I list a removeAnnotation() exception but I've seen tons of exceptions for addAnnotation() as well. I usually get these when opening/closing files. Wed Dec 05 00:46:44 EST 2001: java.lang.NullPointerException: <no message> java.lang.NullPointerException at org.netbeans.modules.editor.NbEditorDocument.removeAnnotation(NbEditorDocument.java:177) at org.openide.text.NbDocument$3.run(NbDocument.java:381) [catch] at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java(Compiled Code)) at java.awt.EventQueue.dispatchEvent(EventQueue.java(Compiled Code)) at java.awt.EventDispatchThread.pumpOneEvent(EventDispatchThread.java(Compiled Code)) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java(Compiled Code)) at java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
It is hard to reproduce the problem from your description. Could you be please more specific. Is the problem somehow reproducible? Which kind of annotations do you use? Breakpoints? Bookmarks? Does it happen always when you open some document, set some breakpoints, close the document and open the same document again? Please give us as much detailes as you can. There is one bug for debugger which causes exactly the same exception, but maybe the cause is different. However, this problem is so annoying and has appeared so many times that I decided to put into the code some more diagnostic messages which should help us in future to analyze which annotations caused the problem.
Seems to me this occurs when I double click on errors listed in the output window, the window pops open and some sort of error-annotation is set. When I save the file or close it, it tries removing the annotation and gets that error. Note sometimes it has errors adding the annotation in the 1st place (when opening the file). BTW: Thanks for extra debugging code, it'll help a lot :)
Hi, I have one quite reproducible case. The exception looks differently from Gili's, so I am attaching it to the bug. Steps: 1. Open any file in editor 2. Make here some errors, so it can not be compiled. 3. Compile it. 4. Double click on error in output window 5. Close the editor 6. Open the editor 7. Double click on the error again. Quite often the NullPointerException will occur. I am not sure whether this is problem of editor or OutputWindow. The above steps looked very reproducible on build 200112062300 (the attached exception is from this build).
Created attachment 3733 [details] The exception thrown.
CCing core.
*** Issue 18674 has been marked as a duplicate of this issue. ***
*** Issue 18885 has been marked as a duplicate of this issue. ***
*** Issue 18958 has been marked as a duplicate of this issue. ***
I was able to reproduce it and I discovered that this problem was caused by the regression in issue 18518! Issue 18518 was already fixed and now this work as well. So I'm marking the issue as FIXED. I will add (for 3.3.1) some logging which should help udentify at least which type of annotation failed.
Resolved for 3.3.x or earlier, no new info since then -> closing.