Eclipse/Webkit browser crashes on Linux

[Phillipus]

Describe the bug
The internal Browser is not rendering on Linux.

To Reproduce
Install latest Eclipse on Ubuntu 23.04 (X11 not Wayland) or Linux Mint 21.2 and do one of the following:

• Open up the internal Browser and try to view a URL
• Open the Welcome page to try to view the content
• Hover over some Java to invoke the tooltip
• Run a basic SWT Snippet to launch a Browser component and set the URL

Either the browser is blank, or sometimes using the Internal Browser View in Eclipse you might see a little of the content. It also seems to be hanging because there is a long delay closing Eclipse.

Expected behavior
Browser component should render on Linux.

Environment:

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

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

2. Additional OS info (e.g. OS version, Linux Desktop, etc)

Ubuntu 23.04
GTK 3.24.37

or:

Linux Mint 21.2
GTK 3.24.33

5. JRE/JDK version

Temurin-17.0.8+7 (build 17.0.8+7)

Version since
Tested on Eclipse 4.27 and later

Workaround (or) Additional context
None

[akurtakov]

Do you say it works with Wayland for you?
What is the webkitgtk version you have ? On fedora 39 with webkit2gtk4.1-2.42.1 internal web browser works just fine with both x11 and wayland for me.

[Phillipus]

Do you say it works with Wayland for you?

I've now tested it with Wayland on Ubuntu and it works. But not working with X11.

I can't test Wayland on Linux Mint because that distro only supports X11.

What is the webkitgtk version you have

On Ubuntu I see these versions:

• libwebkit2gtk-4.0-37
• libwebkit2gtk-4.1-0
• libwebkitgtk-6.0-4

[iloveeclipse]

And which webkit is loaded by SWT?

[akurtakov]

What is the webkitgtk version you have

On Ubuntu I see these versions:

* libwebkit2gtk-4.0-37
* libwebkit2gtk-4.1-0
* libwebkitgtk-6.0-4

You would have to be more specific as these are the so names (more or less) but the actual webkitgtk versions are 2.xx.x format (https://webkitgtk.org/) and I'm interested to see whether you have newer or older version (mine is 2.42.1).
Another thing that comes to my mind is to try uninstalling libwebkit2gtk-4.0 and recheck as SWT will prefer the old version (

eclipse.platform.swt/bundles/org.eclipse.swt/Eclipse SWT WebKit/gtk/library/webkitgtk.h

Line 48 in 459dadd

handle = dlopen("libwebkit2gtk-4.0.so.37", LOAD_FLAGS); /* webkit2/libsoup2 */ \

) which may no longer be in the same shape as libwebkit2gtk-4.1. For what it works - Fedora drops 4.0 already.

[Phillipus]

How do I get the specific versions?

[iloveeclipse]

Go to Eclipse about dialog, software configuration, type SWT and get list of variables set by the framework.

[akurtakov]

This is my Debian knowledge maximum - smth like apt show package_name should give you the info.

[Phillipus]

Go to Eclipse about dialog, software configuration, type SWT and get list of variables set by the framework.

Sorry, can't see any libwebkit2gtk info there.

[Phillipus]

OK:

Ubuntu:

libwebkit2gtk-4.0-37:amd64         2.42.1-0ubuntu0.23.04.1
libwebkit2gtk-4.1-0:amd64          2.42.1-0ubuntu0.23.04.1
libwebkitgtk-6.0-4:amd64           2.42.1-0ubuntu0.23.04.1

Linux Mint:

libwebkit2gtk-4.0-37:amd64         2.42.1-0ubuntu0.22.04.1
libwebkit2gtk-4.1-0:amd64          2.42.1-0ubuntu0.22.04.1

[akurtakov]

So same version (difference could come from distro patches still). Please try getting rid of libwebkit2gtk-4.0-37 for the sake of the experiment.

[akurtakov]

You might be hitting https://bugzilla.redhat.com/show_bug.cgi?id=2240428 but I have no idea about debian/ubuntu GL/GLES naming to give you some more hints.

[Phillipus]

Another thing that comes to my mind is to try uninstalling libwebkit2gtk-4.0 and recheck as SWT will prefer the old version

Didn't fix it.

I rolled back to a snapshot of my Linux Mint installation that uses version 2.40.5 of libwebkit2gtk and that was OK. So must be something to do with version changes.

[Phillipus]

More investigations using Linux Mint (non-Wayland), webkitgtk 2.42.1.

Using this snippet:

import org.eclipse.swt.SWT;
import org.eclipse.swt.browser.Browser;
import org.eclipse.swt.layout.GridData;
import org.eclipse.swt.layout.GridLayout;
import org.eclipse.swt.widgets.Button;
import org.eclipse.swt.widgets.Display;
import org.eclipse.swt.widgets.Shell;

public class BrowserTest {

    public static void main(String[] args) {
        final Display display = new Display();

        final Shell shell = new Shell(display);
        shell.setText("Browser Test");
        shell.setLayout(new GridLayout());

        Browser browser = new Browser(shell, SWT.NONE);
        browser.setLayoutData(new GridData(GridData.FILL_BOTH));

        Button button = new Button(shell, SWT.PUSH);
        button.setText("Go");
        button.setLayoutData(new GridData(GridData.FILL_HORIZONTAL));

        button.addListener(SWT.Selection, event -> {
            browser.setUrl("https://www.eclipse.org");
        });

        shell.setSize(900, 700);
        shell.open();

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

        display.dispose();
    }
}

Sometimes some of the website is rendered in the browser component but most times it is blank. Hovering the mouse over the window the cursor changes to indicate links. Pressing a (invisible) link or pressing the "Go" button a second time gives the following error after some time:

SWT call to Webkit timed out after 10000ms. No return value will be provided.
Possible reasons:
1) Problem: Your javascript needs more than 10000ms to execute.
   Solution: Don't run such javascript, it blocks Eclipse's UI. SWT currently allows such code to complete, but this error is thrown 
     and the return value of execute()/evalute() will be false/null.

2) However, if you believe that your application should execute as expected (in under10000 ms),
 then it might be a deadlock in SWT/Browser/webkit2 logic.
 I.e, it might be a bug in SWT (e.g this does not occur on Windows/Cocoa, but occurs on Linux). If you believe it to be a bug in SWT, then
Please report this issue *with steps to reproduce* via:
 https://bugs.eclipse.org/bugs/enter_bug.cgi?alias=&assigned_to=platform-swt-inbox%40eclipse.org&attach_text=&blocked=&bug_file_loc=http%3A%2F%2F&bug_severity=normal&bug_status=NEW&comment=&component=SWT&contenttypeentry=&contenttypemethod=autodetect&contenttypeselection=text%2Fplain&data=&defined_groups=1&dependson=&description=&flag_type-1=X&flag_type-11=X&flag_type-12=X&flag_type-13=X&flag_type-14=X&flag_type-15=X&flag_type-16=X&flag_type-2=X&flag_type-4=X&flag_type-6=X&flag_type-7=X&flag_type-8=X&form_name=enter_bug&keywords=&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Linux&product=Platform&qa_contact=&rep_platform=PC&requestee_type-1=&requestee_type-2=&short_desc=webkit2_BrowserProblem
For bug report, please atatch this stack trace:
java.lang.Throwable: 
	at org.eclipse.swt.browser.WebKit.getStackTrace(WebKit.java:300)
	at org.eclipse.swt.browser.WebKit.getInternalErrorMsg(WebKit.java:293)
	at org.eclipse.swt.browser.WebKit$Webkit2AsyncToSync.execAsyncAndWaitForReturn(WebKit.java:1272)
	at org.eclipse.swt.browser.WebKit$Webkit2AsyncToSync.runjavascript(WebKit.java:1030)
	at org.eclipse.swt.browser.WebKit$Webkit2AsyncToSync.evaluate(WebKit.java:1000)
	at org.eclipse.swt.browser.WebKit.evaluate(WebKit.java:1299)
	at org.eclipse.swt.browser.WebKit.close(WebKit.java:865)
	at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1792)
	at org.eclipse.swt.browser.WebKit.lambda$4(WebKit.java:768)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5855)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1529)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1555)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1534)
	at org.eclipse.swt.widgets.Widget.release(Widget.java:1337)
	at org.eclipse.swt.widgets.Control.release(Control.java:4803)
	at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1560)
	at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:279)
	at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:503)
	at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:3413)
	at org.eclipse.swt.widgets.Widget.release(Widget.java:1344)
	at org.eclipse.swt.widgets.Control.release(Control.java:4803)
	at org.eclipse.swt.widgets.Widget.dispose(Widget.java:543)
	at org.eclipse.swt.widgets.Shell.dispose(Shell.java:3330)
	at org.eclipse.swt.widgets.Shell.closeWidget(Shell.java:694)
	at org.eclipse.swt.widgets.Shell.gtk_delete_event(Shell.java:1537)
	at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2495)
	at org.eclipse.swt.widgets.Control.windowProc(Control.java:6883)
	at org.eclipse.swt.widgets.Display.windowProc(Display.java:6163)
	at org.eclipse.swt.internal.gtk3.GTK3.gtk_main_do_event(Native Method)
	at org.eclipse.swt.widgets.Display.eventProc(Display.java:1597)
	at org.eclipse.swt.internal.gtk3.GTK3.gtk_main_iteration_do(Native Method)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4514)
	at BrowserTest.main(BrowserTest.java:44)

 Additional information about the error is as following:
 The following javascript was executed:
function SWTWebkit2TempFunc1(){return SWTExecuteTemporaryFunctionCLOSE(window);}; SWTWebkit2TempFunc1()

[dabicho]

I've got to google on the issue again
Seems like it's affecting a variety of tools that use webkitgtk 5.42.x webkit browsers

A workaround is to use the environment variable

WEBKIT_DISABLE_COMPOSITING_MODE=1

Since it seems to be about compositing i'm not sure it affects certain 'X' servers, or graphics drivers or even desktop environment

But I was affected with either Xorg or wayland, with kde plasma, gnome and enlightenment on Arch Linux with propietary nvidia 470xx drivers

UPDATE:

The environment variable
WEBKIT_DISABLE_DMABUF_RENDERER=1
works too