• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 370 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CCS V10.2 hangs after starting.

CCS 10.2 hangs after upgrade

Mark Spavin
Prodigy 140 points
Other Parts Discussed in Thread: CC1310

Following an upgrade from 10.1? to 10.2 the IDE fails to open cleanly. The IDE starts to render and then becomes inactive with a constant high CPU load. I am using Windows 10. When I open a second CCS and select a different workspace the second one successfully opens and builds projects. I can only kill the original CCS from task manager. Returning to the original workspace the working IDE it again fails to open with the same partially rendered IDE. There are multiple entries in the log file but all end with the same line (see below).

I have also uninstalled and re-installed 10.2 and get the same partial unresponsive IDE screen.

!ENTRY org.eclipse.e4.ui.workbench 4 0 2021-03-01 11:58:37.696
!MESSAGE Exception occurred while rendering: IDEWindow=org.eclipse.e4.ui.model.application.ui.basic.impl.TrimmedWindowImpl@41e9f86 (tags: [topLevel, shellMaximized], contributorURI: platform:/plugin/org.eclipse.ui.workbench) (widget: Shell {workspace_v10 - rfEasyLinkEchoRx_BF868_CC1310_tirtos_ccs/Common/rfRxTx.c - Code Composer Studio}, renderer: org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer@5e46a125, toBeRendered: true, onTop: false, visible: true, containerData: null, accessibilityPhrase: null) (label: null, iconURI: null, tooltip: null, context: TrimmedWindowImpl (IDEWindow) Context, variables: [], x: 0, y: 0, width: 1384, height: 928)
!STACK 0
java.lang.IllegalArgumentException: Argument not valid
at org.eclipse.swt.SWT.error(SWT.java:4701)
at org.eclipse.swt.SWT.error(SWT.java:4635)
at org.eclipse.swt.SWT.error(SWT.java:4606)
at org.eclipse.swt.graphics.GC.setForeground(GC.java:4344)
at org.eclipse.ui.forms.widgets.Section.onPaint(Section.java:384)
at org.eclipse.ui.forms.widgets.ExpandableComposite.lambda$0(ExpandableComposite.java:574)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4175)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1081)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066)
at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java:1654)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4816)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:348)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4827)
at org.eclipse.swt.internal.win32.OS.UpdateWindow(Native Method)
at org.eclipse.swt.widgets.Decorations.setVisible(Decorations.java:1312)
at org.eclipse.swt.widgets.Shell.setVisible(Shell.java:1958)
at org.eclipse.swt.widgets.Shell.open(Shell.java:1267)
at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.postProcess(WBWRenderer.java:747)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:680)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:768)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:739)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:733)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:717)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1086)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1049)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:660)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:559)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:154)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:150)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
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:657)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:594)
at org.eclipse.equinox.launcher.Main.run(Main.java:1465)

  • 0
    TI__Guru**** 451311 points

    Hello Mark,

    Mark Spavin said:
    When I open a second CCS and select a different workspace the second one successfully opens and builds projects. I can only kill the original CCS from task manager. Returning to the original workspace the working IDE it again fails to open with the same partially rendered IDE.

    It sounds like a corrupted workspace that requires cleaning. It is not that uncommon for this to happen. We recommend periodic cleaning of your workspace regardless of where CCS was updated or not. Please try cleaning it and reimporting the projects to it and see if that helps.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 140 points

    Thanks Ki, this worked.