[claydavidson]

Eclipse version 2018-12
Oracle JAVA 1.8
Darkest Dark theme

After installing Darkest Dark theme the following problem occurs:
Execute three versions of the same JAVA application in separate JVM’s (no problems without darkest-dark installed)
Depending upon parameters, programs may run for hours or for days.
Programs always run to completion successfully.
Eclipse hangs
Error in message box reads something about “An internal error occurred trying to report an internal error”
Log file:

!SESSION 2019-05-15 11:47:24.791 ———————————————–
eclipse.buildId=4.10.0.I20181206-0815
java.version=1.8.0_211
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.java.product -product org.eclipse.epp.package.java.product -product
org.eclipse.epp.package.java.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product -product
org.eclipse.epp.package.java.product -data file:/C:/DATA/eclipse-workspace/ -product org.eclipse.epp.package.java.product

This is a continuation of log file C:\DATA\eclipse-workspace\.metadata\.bak_8.log
Created Time: 2019-05-16 09:58:54.352

!ENTRY org.eclipse.ui 4 0 2019-05-16 09:58:54.353
!MESSAGE Unhandled event loop exception
!STACK 0
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:4621)
at org.eclipse.swt.SWT.error(SWT.java:4510)
at org.eclipse.swt.SWT.error(SWT.java:4481)
at org.eclipse.swt.widgets.Widget.error(Widget.java:451)
at org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:1798)
at org.eclipse.swt.graphics.GC.win32_new(GC.java:5023)
at org.eclipse.swt.widgets.Control.new_GC(Control.java:2165)
at org.eclipse.swt.widgets.Widget.wmPaint(Widget.java:2111)
at org.eclipse.swt.widgets.Control.WM_PAINT(Control.java:5372)
at org.eclipse.swt.widgets.Composite.WM_PAINT(Composite.java:1515)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4825)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4770)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(Native Method)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3545)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:822)
at org.eclipse.jface.window.Window.open(Window.java:798)
at org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.open(InternalErrorDialog.java:85)
at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.openQuestionDialog(IDEWorkbenchErrorHandler.java:193)
at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.handleException(IDEWorkbenchErrorHandler.java:149)
at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler.access$0(IDEWorkbenchErrorHandler.java:141)
at org.eclipse.ui.internal.ide.IDEWorkbenchErrorHandler$1.runInUIThread(IDEWorkbenchErrorHandler.java:116)
at org.eclipse.ui.progress.UIJob.lambda$0(UIJob.java:98)
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:3919)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3550)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:636)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:563)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:151)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
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:400)
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:659)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)
at org.eclipse.equinox.launcher.Main.run(Main.java:1501)

Attachments:

You must be logged in to view attached files.

[Aaron Lara]

Hello Clay!

Sorry you are running into these issues, thanks for the details provided but I’m afraid I cannot tell right now what’s causing it to run out of handles nor how Devstyle (Darkest Dark) is causing that. We need to investigate further to track the real reason. I know there are some tools that can help finding what processes are using too much handles, like Process Explorer, but ir might take time to trace it.

If you are able to detect the process that leaking the handles it would be great. On the other hand we will try to replicate the issue at our end to see if it is related to DevStyle.

Cheers!
Aaron Lara

[Author]

Posts