MATLAB: Do I receive a java.lang.​NullPointe​rException when closing a figure with the plot tools open in MATLAB 7.0.1 (R14SP1)

getcellpaintergettablecellrenderercomponentMATLABnullpointerexception

I plot a function and start plot tools by clicking on the "Show Plot Tools" button on the figure toolbar. After changing the plot and closing the figure, I receive the following error:
 java.lang.NullPointerException
 at com.mathworks.page.plottool.PlotBrowser$BrowserCellRenderer.getTableCellRendererComponent(PlotBrowser.java:2260)
 at com.mathworks.mwswing.MJTable.getCellPainter(MJTable.java:619)
 at com.mathworks.mwswing.MJTable.shouldShowCellViewer(MJTable.java:648)
 at com.mathworks.mwswing.MJTable$LocalMouseListener.mouseMoved(MJTable.java:428)
 at com.mathworks.mwswing.MJTable$LocalMouseListener.mouseEntered(MJTable.java:464)
 at java.awt.AWTEventMulticaster.mouseEntered(Unknown Source)
 at java.awt.AWTEventMulticaster.mouseEntered(Unknown Source)
 at java.awt.Component.processMouseEvent(Unknown Source)
 at com.mathworks.mwswing.MJTable.processMouseEvent(MJTable.java:786)
 at java.awt.Component.processEvent(Unknown Source)
 at java.awt.Container.processEvent(Unknown Source)
 at java.awt.Component.dispatchEventImpl(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.trackMouseEnterExit(Unknown Source)
 at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
 at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
 at java.awt.Container.dispatchEventImpl(Unknown Source)
 at java.awt.Window.dispatchEventImpl(Unknown Source)
 at java.awt.Component.dispatchEvent(Unknown Source)
 at java.awt.EventQueue.dispatchEvent(Unknown Source)
 at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
 <snip>

Best Answer

There is a bug in MATLAB 7.0.1 (R14SP1) when closing a figure with the plot tools open. Unfortunately, there are no known workarounds.
However, this bug has been fixed in Release 14 Service Pack 3 (R14SP3).
Related Question