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.
Opened core/swing/tabcontrol/src/org/netbeans/swing/ tabcontrol/plaf/DefaultTabbedContainerUI. Individually (not with Ctrl-T) commented out lines 306 and 307: // tabDisplayer.addMouseListener (forward); // contentDisplayer.addMouseListener (forward); The exception below occurs. Note that this exception was occuring extremely frequently (almost every time I change any existing lines of code) in some classes, last week. I filed another issue with a similar stack trace, which was fixed, but I guess they are not the same. Note that I have the Navigator module's window open as well - perhaps it is some race condition causing the null? I don't know if it's reproducible without Navigator, but CodeSync is definitely not part of navigator, so something is wrong here. Annotation: Exception occurred in Request Processor java.lang.NullPointerException at org.netbeans.modules.java.codesync.ClassDependencyImpl.getM ethodElement(ClassDependencyImpl.java:536) at org.netbeans.modules.java.codesync.ClassDependencyImpl.sync hronizeMethods(ClassDependencyImpl.java:963) at org.netbeans.modules.java.codesync.ClassDependencyImpl.impl ementFromSuper(ClassDependencyImpl.java:1179) at org.netbeans.modules.java.codesync.ClassDependencyImpl.acce ss$000(ClassDependencyImpl.java:65) at org.netbeans.modules.java.codesync.ClassDependencyImpl$Syn chronizer.collectSupertypeMethods(ClassDependencyImpl.java: 219) at org.netbeans.modules.java.codesync.ClassDependencyImpl$Syn chronizer.run(ClassDependencyImpl.java:209) at org.openide.util.Task.run(Task.java:136) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.ja va:330) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProces sor.java:686)
This is really the same bug as the duplicate and was fixed. From the stacktrace oyu pasted here, it seems your build is ouf of date (getMethodElement is now called from line 965 instead of 963, lines 963 and 964 now contain a check for null which fixed the bug). *** This issue has been marked as a duplicate of 49845 ***