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.
In CCS 12.1, I see that running ROV for a few hours results in its screen becoming blank.
Log shows the following stack trace:
!ENTRY org.eclipse.ui.ide 4 4 2022-11-18 16:16:06.453
!MESSAGE Not properly disposed SWT resource
!STACK 0
java.lang.Error: SWT Resource was not properly disposed
at org.eclipse.swt.graphics.Resource.initNonDisposeTracking(Resource.java:172)
at org.eclipse.swt.graphics.Resource.<init>(Resource.java:120)
at org.eclipse.swt.graphics.Cursor.<init>(Cursor.java:173)
at com.teamdev.jxbrowser.view.swt.internal.SwtCursorFactory.toolkitCursor(SwtCursorFactory.java:45)
at com.teamdev.jxbrowser.view.swt.internal.SwtCursorFactory.defaultCursor(SwtCursorFactory.java:63)
at com.teamdev.jxbrowser.view.swt.internal.SwtCursorFactory.defaultCursor(SwtCursorFactory.java:28)
at com.teamdev.jxbrowser.ui.internal.CursorFactory.standardCursor(CursorFactory.java:65)
at com.teamdev.jxbrowser.ui.internal.CursorFactory.newCursor(CursorFactory.java:45)
at com.teamdev.jxbrowser.view.swt.internal.OffScreenRenderWidget.lambda$showRenderWidget$3(OffScreenRenderWidget.java:168)
at com.teamdev.jxbrowser.view.swt.internal.SafeExecutor.lambda$executeSilently$1(SafeExecutor.java:87)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4320)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3943)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:136)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:401)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.base/java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:596)
at org.eclipse.equinox.launcher.Main.run(Main.java:1467)
Hello Martin,
ROV is using a browser engine to render the GUI. It appears that the fault is coming from that browser engine. We have contacted the vendor with the call stack that you provided. They have confirmed that issue is resolved in a newer version of browser engine. I have opened a ticket for us to update browser engine in CCS.
Martin
here is the link to externally visible ticket ID sir.ext.ti.com/.../EXT_EP-10942
Martin