-
Notifications
You must be signed in to change notification settings - Fork 185
Description
Describe the bug
I started an application that contains a RichTextEditor and get an error on startup:
org.eclipse.swt.SWTException: Waiting for Edge operation to terminate timed out
at org.eclipse.swt.browser.Edge.createTimeOutException(Edge.java:525)
at org.eclipse.swt.browser.Edge.processOSMessagesUntil(Edge.java:520)
at org.eclipse.swt.browser.Edge.callAndWait(Edge.java:287)
at org.eclipse.swt.browser.Edge.evaluate(Edge.java:902)
at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:405)
at org.eclipse.swt.browser.Browser.evaluate(Browser.java:665)
at org.eclipse.swt.browser.Browser.evaluate(Browser.java:614)
at org.eclipse.nebula.widgets.richtext.RichTextEditor$3.completed(RichTextEditor.java:284)
at org.eclipse.swt.browser.Edge.lambda$45(Edge.java:1109)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:40)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:132)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4094)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3710)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1151)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1042)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
at org.eclipse.e4.ui.internal.workbench.swt.E4Application.start(E4Application.java:165)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:208)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:149)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:115)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:467)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:298)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:607)
at org.eclipse.equinox.launcher.Main.run(Main.java:1492)
at org.eclipse.equinox.launcher.Main.main(Main.java:1465)
Might be a duplicate of #1771
To Reproduce
- Checkout https://github.com/EclipseNebula/nebula
- Locate
org.eclipse.nebula.widgets.richtext.example - Open the file
org.eclipse.nebula.widgets.richtext.example.RichTextEditorExample - Run the
mainmethod
Note:
You first need to locally fix org.eclipse.nebula.widgets.richtext.RichTextEditor#setBounds(int, int, int , int) and replace line 757 with
super.setBounds(new Rectangle(newX, newY, newWidth, newHeight));The call stack in SWT Control was changed which now leads to a StackOverflowError as reported in EclipseNebula/nebula#631. While trying to fix this, I came across this issue. I need to find a way to verify if the fix works before I actually can push it.
Expected behavior
A shell should open and show the RichTextEditor.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment:
- Select the platform(s) on which the behavior is seen:
-
- All OS
-
- Windows
-
- Linux
-
- macOS
-
Additional OS info (e.g. OS version, Linux Desktop, etc)
-
JRE/JDK version
Version since
Eclipse or SWT version since when the behavior is seen [e.g. 4.23]
Workaround (or) Additional context
Add any other context about the problem here.
Any known workarounds for the problem?