Edge browser engine does not properly load BrowserFunction

[azoitl]

When using the Nebula RichtTextEditor in our Eclipse RCP (4diac IDE) on Windows we get an SWTException with getAllOptions is not defined at reported by org.eclipse.swt.browser.Edge.evaluateInternal(Edge.java:960). See also the full stack trace below.

We tested this on latest Eclipse 2025-09 Milestone.

Unhandled event loop exception

Stack Trace:

org.eclipse.swt.SWTException: getAllOptions is not defined
	at org.eclipse.swt.browser.Edge.evaluateInternal(Edge.java:960)
	at org.eclipse.swt.browser.Edge.evaluate(Edge.java:933)
	at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:405)
	at org.eclipse.swt.browser.Browser.evaluate(Browser.java:731)
	at org.eclipse.swt.browser.Browser.evaluate(Browser.java:680)
	at org.eclipse.nebula.widgets.richtext.RichTextEditor$3.completed(RichTextEditor.java:285)
	at org.eclipse.swt.browser.Edge.lambda$43(Edge.java:1176)
	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:4133)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3749)
	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.ui.internal.Workbench.lambda$3(Workbench.java:678)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:583)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:185)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:219)
	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.DirectMethodHandleAccessor.invoke(Unknown Source)
	at java.base/java.lang.reflect.Method.invoke(Unknown Source)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:627)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1431)

Environment:

1. Select the platform(s) on which the behavior is seen:

• • All OS
• • Windows
• • Linux
• • macOS

[merks]

FYI, this blank line is important to format the following content via the triple back quote.

[merks]

The stack trace line numbers don't align with the current code base... Can you find out which exact version of SWT is involved?

[azoitl]

@merks sorry my fault I only verified if the issue persists on the latest Eclipse Platform Milestone Release but I copied the originally provided stack trace from an Eclipse 4diac user.

I now recreated everything and I tested with:

• https://download.eclipse.org/releases/2025-09
  • org.eclipse.swt.win32.win32.x86_64_3.131.0.v20250814-2121.jar
  • org.eclipse.swt_3.131.0.v20250814-2121.jar

The updated stack trace for this SWT version is:

Unhandled event loop exception getAllOptions is not defined
  org.eclipse.swt.SWTException: getAllOptions is not defined
  	at org.eclipse.swt.browser.Edge.evaluateInternal(Edge.java:962)
  	at org.eclipse.swt.browser.Edge.evaluate(Edge.java:935)
  	at org.eclipse.swt.browser.WebBrowser.evaluate(WebBrowser.java:405)
  	at org.eclipse.swt.browser.Browser.evaluate(Browser.java:734)
  	at org.eclipse.swt.browser.Browser.evaluate(Browser.java:683)
  	at org.eclipse.nebula.widgets.richtext.RichTextEditor$3.completed(RichTextEditor.java:285)
  	at org.eclipse.swt.browser.Edge.lambda$43(Edge.java:1178)
  	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:4135)
  	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3751)
  	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.ui.internal.Workbench.lambda$3(Workbench.java:678)
  	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:339)
  	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:583)
  	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:173)
  	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:185)
  	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:219)
  	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.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
  	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
  	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:627)
  	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
  	at org.eclipse.equinox.launcher.Main.run(Main.java:1431)
  	at org.eclipse.equinox.launcher.Main.main(Main.java:1403)

[merks]

It looks like the caller is defining a function here:

https://github.com/EclipseNebula/nebula/blob/7cf9d9db55bec3208418249ad25637d05befacb5/widgets/richtext/org.eclipse.nebula.widgets.richtext/src/org/eclipse/nebula/widgets/richtext/RichTextEditor.java#L265-L285

I think having a pure SWT reproducer of the problem is needed...

[HeikoKlare]

At a first glance, the code looks as if it should work as expected, i.e., that the getAllOptions function is registered when the completion listener is called.
The methods calls should behave similiar (in terms of synchronous/asynchronous behavior) than on IE or others browser. Except for setUrl(), which is now asynchronous but the subsequent new BrowserFunction() calls should trigger a synchronization again.

So yes, we probably need to strip down the code to a pure and small SWT reproducer.

Is this a new issue with 2025-09 or has it already existed in the previous release?

[azoitl]

I tested a bit further and noticed that it only happens when more then one instance of the rich text editor is created (we have it in a tab of a multi-page editor).

I think I have seen it already with 2025-03. But there where other issues with Nebula's Richtext editor.

[HeikoKlare]

That's interesting. Thank you for the additional information! And are you sure it just happens with Edge and not any other browser? On Windows you could test with -Dorg.eclipse.swt.browser.DefaultType=IE to see if it also happens with internet explorer.

[azoitl]

Yes I'm sure it just happens with Edge. Our workaround for Windows is now to use IE: eclipse-4diac/4diac-ide#1575

[HeikoKlare]

Here is a rather simple snippet to reproduce. It does not always crash but for me it crashes in most of the cases.
Note that the Thread.sleep(100) is important. Without it or with a much higher sleep value, the problem does not occur. With RichTextEditor it happens because that's the time it takes to initialize all the controls. Once I removed control intialization, it started to work. So this seems to be some timing issue.

import org.eclipse.swt.*;
import org.eclipse.swt.browser.*;
import org.eclipse.swt.layout.*;
import org.eclipse.swt.widgets.*;

public class SnippetEdgeFunctionException {

	public static void main(String[] args) throws InterruptedException {
		Display display = new Display();
		Shell shell = new Shell(display);
		shell.setLayout(new FillLayout());

		createBrowser(shell);
		Thread.sleep(100);
		createBrowser(shell);

		shell.open();
		while (!shell.isDisposed()) {
			if (!display.readAndDispatch())
				display.sleep();
		}
		display.dispose();
	}

	private static void createBrowser(Shell shell) {
		Browser browser = new Browser(shell, SWT.None);
		browser.setUrl("about:blank");

		new BrowserFunction(browser, "options") {
			@Override
			public Object function(final Object[] arguments) {
				return null;
			}
		};

		browser.addProgressListener(new ProgressListener() {
			@Override
			public void completed(final ProgressEvent event) {
				browser.evaluate("options();");
			}

			@Override
			public void changed(ProgressEvent event) {
			}
		});
	}

}

[HeikoKlare]

And I guess this is probably related to (or even the same as):

• [Edge][BrowserFunction] BrowserFunctions added to window undefined when URL loaded #20