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.
A null pointer is encountered when doing memory profiling (Netbeans 4.0RC2, Profiler M3V2) java.lang.NullPointerException at com.sun.tools.profiler.ui.memory.MemoryResultsPanel.doCreateClassNamesFromScratch(MemoryResultsPanel.java:366) at com.sun.tools.profiler.ui.memory.MemoryResultsPanel.sortResultsByClassName(MemoryResultsPanel.java:295) at com.sun.tools.profiler.ui.memory.ObjLivenessResultsPanel.getResultsSortedByClassName(ObjLivenessResultsPanel.java:361) at com.sun.tools.profiler.ui.memory.ObjLivenessResultsPanel.getResultsSortedByLiveObjSize(ObjLivenessResultsPanel.java:378 ) at com.sun.tools.profiler.ui.memory.ObjLivenessResultsPanel.getResultsTable(ObjLivenessResultsPanel.java:238) at com.sun.tools.profiler.ui.memory.MemoryResultsPanel.prepareResults(MemoryResultsPanel.java:71) at org.netbeans.netfluid.ResultsWindow.updateLivenessResults(ResultsWindow.java:479) at org.netbeans.netfluid.ResultsWindow.updateResults(ResultsWindow.java:365) at org.netbeans.netfluid.ResultsWindow.getResults(ResultsWindow.java:345) at org.netbeans.netfluid.actions.GetCurrentResultsAction.performAction(GetCurrentResultsAction.java:36) at org.openide.util.actions.CallableSystemAction$1.run(CallableSystemAction.java:78) at org.openide.util.actions.CallableSystemAction.doPerformAction(CallableSystemAction.java:116) at org.openide.util.actions.CallableSystemAction.actionPerformed(CallableSystemAction.java:76) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1786) at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(AbstractButton.java:1839) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258) at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:245) at java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:231) at java.awt.Component.processMouseEvent(Component.java:5100) at org.openide.awt.ToolbarButton.processMouseEvent(ToolbarButton.java:29) at java.awt.Component.processEvent(Component.java:4897) at java.awt.Container.processEvent(Container.java:1569) at java.awt.Component.dispatchEventImpl(Component.java:3615) at java.awt.Container.dispatchEventImpl(Container.java:1627) at java.awt.Component.dispatchEvent(Component.java:3477) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:3483) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3198) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3128) at java.awt.Container.dispatchEventImpl(Container.java:1613) at java.awt.Window.dispatchEventImpl(Window.java:1606) at java.awt.Component.dispatchEvent(Component.java:3477) at java.awt.EventQueue.dispatchEvent(EventQueue.java:456) [catch] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137) at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
This issue is most likely fixed in the forthcoming M4 release. But since some bugs in this area weren't tracked in Issuezilla, I can't be sure about that. So the best thing would be for us to send you a "patch" - several JAR files which will convert your JFluid installation into the M4 release preview. Then you can check whether this bug has gone away and/or if there are any issues with this new release, which we would appreciate a lot. If you would like to get a patch, please check that your e-mail system can accept large (500-600K) binary attachments. Misha Dmitriev JFluid/NetBeans Profiler Team
Yes, please... can you send me the patch? Thanks!
This defect is not solved by the patch.
I was debugging a process running Ant. Ant has several jar files that reference other classes, but are only used if the other classes are on the classpath. Also, the process was using RMI to connect to another process -- which may have contributed to the problem. In any case, I removed most of the unused Ant jars from the classpath, and this seems to have partially solved the problem. I'm away now for a few days so won't be able to regenerate the problem until I get back.
Ok, if the problem hasn't gone away, could you please provide the updated stack trace for the crash? In our current code the line numbers are quite different, so it's difficult to understand where this problem originates.
Since I didn't get any further info on this issue so far, I assume it doesn't show up anymore, and close this issue for now.
Verification of old issues.
Closing old issues.