This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS-5.2.1 Bug Report: NullPointerException when closing CCS with debug perspective open

Hi,

Just experenced a situation where it was not possible to close CCS-5.2.1 for Windows anymore.
Every time I tried to close it using the window-close-button, a NullPointerException was triggered, this is the complete stack trace:

java.lang.NullPointerException at com.ti.util.ui.PartManager.getView(PartManager.java:370) at com.ti.util.ui.PartManager.getViewPart(PartManager.java:94) at com.ti.dvt.via.plugin.ccs.ActivatorCCS.persistImageProperties(ActivatorCCS.java:339) at com.ti.dvt.via.plugin.ccs.ActivatorCCS.preShutdown(ActivatorCCS.java:322) at org.eclipse.ui.internal.Workbench$10.run(Workbench.java:912) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.ui.internal.Workbench.firePreShutdown(Workbench.java:910) at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1050) at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040) at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282) at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254) at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:727) at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715) at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865) at org.eclipse.jface.window.Window.handleShellCloseEvent(Window.java:741) at org.eclipse.jface.window.Window$3.shellClosed(Window.java:687) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:98) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Decorations.closeWidget(Decorations.java:308) at org.eclipse.swt.widgets.Decorations.WM_CLOSE(Decorations.java:1677) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4530) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native Method) at org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:2526) at org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:498) at org.eclipse.swt.widgets.Control.windowProc(Control.java:4623) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:341) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1610) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2061) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4972) at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2531) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3752) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

@Lisa: Plase submit this report to the development team ;)

Thanks, Clemens

  • Hi Clemens,

    I will do my best for you.

    A few questions here.  Is this reproducable?  Ie does this happen every time?  Or every time afer a certain sequence of events?  If so what steps do you take to trigger this? 

    Do you have any further diagnostics/information you could provide. Have you enabled the following logs ... if generated could you send those?

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

    Best Regards,

    Lisa

  • Hi Clemens,

    In addition to Lisa questions. If you're able to reproduce this can you let us know if you have an Image Analyzer view open when you try to close CCS? If so can you try closing the Image Analyzer view and see if CCS closes without error. 

    If you're not able to reproduce it and don't have an Image Analyzer view open can you try opening one and see if that brings the problem back. I am assuming that you were using Image Analyzer at some point ... is this correct?

    Regards,

    Imtaz.

  • Hi Imtaz,

    Yes, there is an Image Analyzer open (although not visible, hidden behind another tab) - that also explains why I got the Exception only in debug view.

    Hope this helps, Clemens

  • Clemens,

    This does help (along with the stack information you provided earlier). It appears that there is a problem with the view is hidden. We've file a CQ (SDSCM00045657) to track this issues and will be fixing it in CCS5.4.

    Regards,

    Imtaz.