• Locked Locked
  • Replies 7 replies
  • Subscribers 55 subscribers
  • Views 818 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCStudio v5 crashing while opening project

Natraj Krishnappa
Prodigy 10 points
Other Parts Discussed in Thread: CCSTUDIO

Hi,

I have installed CCStudio v5 on my windows 7. The installation was successfully while opening up CCS.exe icon prompt me to default workspace and then I see  dialogue error message coming up. Problem Occured " An unexpected runtime error has occured".  It prompts me to open up \.metadata\log file and i see below error message in log file.


!ENTRY org.eclipse.osgi 4 0 2015-12-10 13:04:57.785
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:4308)
at org.eclipse.swt.SWT.error(SWT.java:4197)
at org.eclipse.swt.SWT.error(SWT.java:4168)
at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
at org.eclipse.swt.widgets.TaskBar.createHandle(TaskBar.java:103)
at org.eclipse.swt.widgets.TaskBar.<init>(TaskBar.java:96)
at org.eclipse.swt.widgets.Display.getSystemTaskBar(Display.java:2564)
at org.eclipse.ui.internal.WorkbenchWindow.createProgressIndicator(WorkbenchWindow.java:3362)
at org.eclipse.ui.internal.WorkbenchWindow.createDefaultContents(WorkbenchWindow.java:1130)
at org.eclipse.ui.internal.WorkbenchWindowConfigurer.createDefaultContents(WorkbenchWindowConfigurer.java:623)
at org.eclipse.ui.application.WorkbenchWindowAdvisor.createWindowContents(WorkbenchWindowAdvisor.java:300)
at org.eclipse.ui.internal.WorkbenchWindow.createContents(WorkbenchWindow.java:1036)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.ui.internal.Workbench$22.runWithException(Workbench.java:1211)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
at org.eclipse.ui.internal.Workbench$33.runWithException(Workbench.java:1595)
at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
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)

!ENTRY org.eclipse.core.jobs 2 2 2015-12-10 13:04:58.155
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.AbstractWorkingSetManager$10

!ENTRY org.eclipse.core.jobs 2 2 2015-12-10 13:04:58.155
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.AbstractWorkingSetManager$10

!ENTRY org.eclipse.core.jobs 2 2 2015-12-10 13:04:58.155
!MESSAGE Job found still running after platform shutdown. Jobs should be canceled by the plugin that scheduled them during shutdown: org.eclipse.ui.internal.AbstractWorkingSetManager$10

Later on CCstudio crashes.

Please can someone provide me pointers how to fix the issue. 

Thank You,

Raj

  • TI__Guru**** 464431 points

    Hi Raj,

    The error you see can have several potential causes. One is conflict with other software running on your computer. Some known ones are programs that adds some buttons to window title bars (like displayfusion or teamviewer). Do you have any such programs installed?

    https://bugs.eclipse.org/bugs/show_bug.cgi?id=402983

    Another related issue was caused by a virus (removing the virus resolved the issue).

    If the neither turn out to be the cause, can you zip up the .metadata folder in your workspace and attach it to this thread?


    Thanks

    ki

  • TI__Intellectual 1065 points
    Hey Raj, I support Neato locally and sent you email introducing your local support folks
  • in reply to Ki
    TI__Intellectual 2555 points

    Hi Ki,  I have attached the zipped up the .metadata folder.  Raj has checked for unwanted software, disabled antivirus during install, and tried re-installing, but is seeing the issue shown below.  Raj has also tried to capture error with (.dmp) logs for use using  C tools/ Trace logging, per our online instructions here, but is not able to find any log file with in "/ccsv5/ccs_base/emulation/analysis/bin/Logs."  Can you tell us what the file name should be and possibly why it is not there?

    .metadata.zip

    Thanks,

    kelvin

  • in reply to Kelvin
    TI__Guru**** 464431 points

    Kelvin said:
     I have attached the zipped up the .metadata folder. 

    great, thank you. I will have the engineering team analyze it and keep you posted of the progress.

    Kelvin said:
    Raj has also tried to capture error with (.dmp) logs for use using  C tools/ Trace logging, per our online instructions here, but is not able to find any log file with in "/ccsv5/ccs_base/emulation/analysis/bin/Logs."  Can you tell us what the file name should be and possibly why it is not there?

    The DS and Trace logging would only start capturing data once a debug session has started. Otherwise no log will be generated.


    Thanks

    ki

  • in reply to Ki
    TI__Guru**** 464431 points
    One last thing to try... does using a clean new workspace folder help at all?
  • in reply to Ki
    TI__Intellectual 2555 points
    Thanks Ki,

    Raj has followed the steps below to try to start the debugging session. Is there something missing here:
    1. Quit CCS.
    2. Right click on the “MyComputer” icon on your desktop.
    3. Select “Properties”.
    4. Win7 on "Advanced System Settings"
    5. In the System Properties dialog, clicked on the “Advanced” tab.
    6. Clicked on the “Environment Variables” button. In the “Environment Variables” dialog
    7. Under the “User variables” group, verified that the “TI_TRACE_LOGGING” environment variable existed not present in my case, so added it with a value of 6. (Created as it was not presented).
    8. Clicked “OK” in all dialogs. Restart CCS.
    9. Reproduce the problem, noting what steps were performed in what order.

    Kelvin
  • in reply to Kelvin
    TI__Guru**** 464431 points
    Kelvin,
    Raj is hitting the error before he even gets a chance to start a debug session. He gets the error when trying to launch CCS. The trace/ds logs will only capture data related to a running debug session.