Eclipse IDE crashing with Java errors since 22.04 upgrade when using wayland

[Roger C-O]

Eclipse IDE (2022-06 updated since 2019-09) crashing since Ubuntu updated 20.04 -> 22.04.01

Happens several times daily with no obvious pattern.

Most recent log (or the first chunk of it, another 400kB available):
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f087124c316, pid=105292, tid=105293
#
# JRE version: OpenJDK Runtime Environment (11.0.16+8) (build 11.0.16+8-post-Ubuntu-0ubuntu122.04)
# Java VM: OpenJDK 64-Bit Server VM (11.0.16+8-post-Ubuntu-0ubuntu122.04, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libwebkit2gtk-4.0.so.37+0xbc8316]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to /home/roger/core.105292)
#
# If you would like to submit a bug report, please visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-lts
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

--------------- S U M M A R Y ------------

Command Line: -Declipse.p2.max.threads=10 -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/ -Dosgi.requiredJavaVersion=11 -<email address hidden>/eclipse-workspace -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=11 -Dosgi.dataAreaRequiresExplicitInit=true -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Xms256m -Xmx2048m --add-modules=ALL-SYSTEM /home/roger/eclipse/php-2020-06/eclipse//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar -os linux -ws gtk -arch x86_64 -showsplash /home/roger/.p2/pool/plugins/org.eclipse.epp.package.common_4.24.0.20220609-1200/splash.bmp -launcher /home/roger/eclipse/php-2020-06/eclipse/eclipse -name Eclipse --launcher.library /home/roger/.p2/pool/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.500.v20220509-0833/eclipse_11701.so -startup /home/roger/eclipse/php-2020-06/eclipse//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar --launcher.appendVmargs -exitdata 30022 -product org.eclipse.epp.package.php.product -vm /usr/bin/java -vmargs -Declipse.p2.max.threads=10 -Doomph.update.url=http://download.eclipse.org/oomph/updates/milestone/latest -Doomph.redirection.index.redirection=index:/->http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/ -Dosgi.requiredJavaVersion=11 -<email address hidden>/eclipse-workspace -Dsun.java.command=Eclipse -XX:+UseG1GC -XX:+UseStringDeduplication --add-modules=ALL-SYSTEM -Dosgi.requiredJavaVersion=11 -Dosgi.dataAreaRequiresExplicitInit=true -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Xms256m -Xmx2048m --add-modules=ALL-SYSTEM -jar /home/roger/eclipse/php-2020-06/eclipse//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar

Host: Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz, 4 cores, 7G, Ubuntu 22.04.1 LTS
Time: Tue Sep 6 13:11:08 2022 BST elapsed time: 3918.751234 seconds (0d 1h 5m 18s)

--------------- T H R E A D ---------------

Current thread (0x00007f0928017000): JavaThread "main" [_thread_in_native, id=105293, stack(0x00007f092dbf6000,0x00007f092dcf6000)]

Stack: [0x00007f092dbf6000,0x00007f092dcf6000], sp=0x00007f092dcf3438, free space=1013k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libwebkit2gtk-4.0.so.37+0xbc8316]

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 6197 org.eclipse.swt.internal.gtk.OS.g_object_unref(J)V (0 bytes) @ 0x00007f09185ec911 [0x00007f09185ec8c0+0x0000000000000051]
j org.eclipse.swt.browser.WebKit.lambda$8(J)V+1
j org.eclipse.swt.browser.WebKit$$Lambda$1197.run()V+4
J 19197 c2 org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Z)Z (188 bytes) @ 0x00007f0918744fa4 [0x00007f0918744bc0+0x00000000000003e4]
J 35449 c2 org.eclipse.swt.widgets.Display.readAndDispatch()Z (88 bytes) @ 0x00007f0919eae6a4 [0x00007f0919eae580+0x0000000000000124]
J 23143% c2 org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run()V (690 bytes) @ 0x00007f0918ff5278 [0x00007f0918ff50e0+0x0000000000000198]
j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12
j org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(Lorg/eclipse/e4/ui/model/application/MApplicationElement;Lorg/eclipse/e4/core/contexts/IEclipseContext;)Ljava/lang/Object;+57
j org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(Lorg/eclipse/e4/ui/model/application/MApplicationElement;)V+20
j org.eclipse.ui.internal.Workbench.lambda$3(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;[I)V+393
j org.eclipse.ui.internal.Workbench$$Lambda$145.run()V+12
j org.eclipse.core.databinding.observable.Realm.runWithDefault(Lorg/eclipse/core/databinding/observable/Realm;Ljava/lang/Runnable;)V+12
j org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+16
j org.eclipse.ui.PlatformUI.createAndRunWorkbench(Lorg/eclipse/swt/widgets/Display;Lorg/eclipse/ui/application/WorkbenchAdvisor;)I+2
j org.eclipse.ui.internal.ide.application.IDEApplication.start(Lorg/eclipse/equinox/app/IApplicationContext;)Ljava/lang/Object;+113
j org.eclipse.equinox.internal.app.EclipseAppHandle.run(Ljava/lang/Object;)Ljava/lang/Object;+138
j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Ljava/lang/Object;)Ljava/lang/Object;+85
j org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Ljava/lang/Object;)Ljava/lang/Object;+79
j org.eclipse.core.runtime.adaptor.EclipseStarter.run(Ljava/lang/Object;)Ljava/lang/Object;+99
j org.eclipse.core.runtime.adaptor.EclipseStarter.run([Ljava/lang/String;Ljava/lang/Runnable;)Ljava/lang/Object;+132
v ~StubRoutines::call_stub
j jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/reflect/Method;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0 java.base@11.0.16
j jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+100 java.base@11.0.16
j jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6 java.base@11.0.16
j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+59 java.base@11.0.16
j org.eclipse.equinox.launcher.Main.invokeFramework([Ljava/lang/String;[Ljava/net/URL;)V+201
j org.eclipse.equinox.launcher.Main.basicRun([Ljava/lang/String;)V+159
j org.eclipse.equinox.launcher.Main.run([Ljava/lang/String;)I+4
j org.eclipse.equinox.launcher.Main.main([Ljava/lang/String;)V+10
v ~StubRoutines::call_stub

siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x0000000000000000

Plus another 400k of stuff...

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pascal Girard (pascal100)]

Hello,

I have exactly the same bug in the same context, since the I did the upgrade (8 days).
If a quick solution is not found, I will have to abandon Eclipse because with this bug I can no longer continue my developments.
I tried old versions of Eclipse but with Ubuntu 22.04, they don't work.
With Ubuntu 20.04 version I had no problem with Eclipse.

Best regards

[Pascal Girard (pascal100)]

Hello,

Finally I installed Eclipse IDE 2022-09 (latest) and I saw on this post (https://github.com/eclipse-platform/eclipse.platform.swt/issues/158) that the problem may come from wayland.
So I switched to X11 and my Eclipse runs well !!!

[Roger C-O (rogerco)]

Many thanks to Pascal in comment #3 - switching back to X11 seems to fix this and several other minor annoyances with 22.04. It seems Wayland is not reliable and should be selectable as an option when upgrading from 20.04 rather than being imposed as a default.

Eclipse also seems to be much faster (as it used to be) using X11

Perhaps the enforced change to Wayland was a fundamental mistake until it has been better tested in the real world and could be reverted in the next release. Since the option is available on the user login screen (the gear icon once the password box is visible it should be easy to make it an upgrade option with appropriate warning that some existing applications may become unstable..

Many users (like me) probably never see the login screen as they have only one user on the device and it boots straight into that user - I have never used the logout screen before, always just power off. So that is going to be another usability annoyance if I have to logout after power off every time to switch to X11 - unless I permanently disable Wayland which begs the question what is the point of it.

[Samir Kamerkar (samirkamerkar)]

This issue has been traced down the stack through the epiphany browser widget[1] -> webkit -> mesa[2].

A suggested narrowed down workaround via [1]-
------
[Desktop Entry]
Name=Eclipse IDE
Exec=env WEBKIT_DISABLE_COMPOSITING_MODE=1 /home/pdallig/Apps/eclipse-ide-2021-12/eclipse
Comment=Eclipse
Terminal=false
Icon=/home/pdallig/Apps/eclipse-ide-2021-12/icon.xpm
Type=Application
------

A bug has been confirmed and fixed on the Mesa package for 22.04 as well. [2]

1. https://github.com/eclipse-platform/eclipse.platform.swt/issues/158#issuecomment-1276431212
2. https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418

[Jean-Paul Poulet (jp-poulet)]

same problem with Ubuntu 22.04.1 + Gnome 42.5 + Wayland
switching back to X11 seems to fix the problem
Many thanks to Pascal in comment #3 and Roger in comment #4

[David Wu (amidavidw)]

I had the same issue before.
By turning off Wayland, it worked until some recent Ubuntu updates.

Now Ubuntu crashes, when I try to rename something in Java code using the refactoring function of eclipse.

Most of the time, the Ubuntu screen becomes black and I have to force restart it.
Occasionally, it shows some console outputs as in the attachment.

My eclipse is an updated version from 2022-12 to 2023-03.

I downloaded an original eclipse 2023-03.
For this instance, Ubuntu crashes (black screen) when I try to maximize eclipse main window.

I hope the information is useful to fix the issue.

Eclipse: 2023-03 updated from 2022-12
Ubuntu: 22.04 (updated daily) on VMPlayer 17

[Jorge (jjcampos)]

The same thing started happening to me from Yesterday evening. After a bunch of tries and attempts I was able to have it working if I disable login without Wayland.

It started on Eclipse 2023-06 then I downgraded it to 2023-03, fresh workspace, same error. As soon as I hover the mouse on an identifier it crashes.

My Ubuntu:
Distributor ID: Ubuntu
Description: Ubuntu 22.04.2 LTS
Release: 22.04
Codename: jammy

I'm running openjdk Temurin:
openjdk version "17.0.7" 2023-04-18
OpenJDK Runtime Environment Temurin-17.0.7+7 (build 17.0.7+7)
OpenJDK 64-Bit Server VM Temurin-17.0.7+7 (build 17.0.7+7, mixed mode, sharing)

I did notice some unattended upgrades yesterday, I will try to attach both the list of unattended and the hs_pid file from eclipse.

I'm also attaching the Eclipse hs_pid error file

=======================
jorge@hq-l0b0f /var/log/apt $ cat history.log

Start-Date: 2023-07-03 06:19:35
Commandline: /usr/bin/unattended-upgrade
Upgrade: vim:amd64 (2:8.2.3995-1ubuntu2.8, 2:8.2.3995-1ubuntu2.9), vim-common:amd64 (2:8.2.3995-1ubuntu2.8, 2:8.2.3995-1ubuntu2.9), vim-tiny:amd64 (2:8.2.3995-1ubuntu2.8, 2:8.2.3995-1ubuntu2.9), vim-runtime:amd64 (2:8.2.3995-1ubuntu2.8, 2:8.2.3995-1ubuntu2.9)
End-Date: 2023-07-03 06:19:38

Start-Date: 2023-07-03 06:19:39
Commandline: /usr/bin/unattended-upgrade
Upgrade: xxd:amd64 (2:8.2.3995-1ubuntu2.8, 2:8.2.3995-1ubuntu2.9)
End-Date: 2023-07-03 06:19:40

Start-Date: 2023-07-04 06:47:17
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-renderpm:amd64 (3.6.8-1, 3.6.8-1ubuntu0.1)
End-Date: 2023-07-04 06:47:18

Start-Date: 2023-07-04 06:47:19
Commandline: /usr/bin/unattended-upgrade
Upgrade: python3-reportlab-accel:amd64 (3.6.8-1, 3.6.8-1ubuntu0.1), python3-reportlab:amd64 (3.6.8-1, 3.6.8-1ubuntu0.1)
End-Date: 2023-07-04 06:47:21

Start-Date: 2023-07-04 09:28:36
Commandline: aptdaemon role='role-commit-packages' sender=':1.509'
Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2)
End-Date: 2023-07-04 09:28:38

Start-Date: 2023-07-05 06:45:01
Commandline: /usr/bin/unattended-upgrade
Upgrade: containerd:amd64 (1.6.12-0ubuntu1~22.04.1, 1.6.12-0ubuntu1~22.04.3)
End-Date: 2023-07-05 06:45:03

Start-Date: 2023-07-10 06:51:00
Commandline: /usr/bin/unattended-upgrade
Upgrade: libllvm15:amd64 (1:15.0.7-0ubuntu0.22.04.1, 1:15.0.7-0ubuntu0.22.04.2)
End-Date: 2023-07-10 06:51:01

Start-Date: 2023-07-11 06:25:01
Commandline: /usr/bin/unattended-upgrade
Upgrade: ghostscript-x:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9-common:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), ghostscript:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3), libgs9:amd64 (9.55.0~dfsg1-0ubuntu5.2, 9.55.0~dfsg1-0ubuntu5.3)
End-Date: 2023-07-11 06:25:03

Start-Date: 2023-07-11 06:25:05
Commandline: /usr/bin/unattended-upgrade
Upgrade: thunderbird:amd64 (1:102.11.0+build1-0ubuntu0.22.04.1, 1:102.13.0+build1-0ubuntu0.22.04.1), thunderbird-gnome-support:amd64 (1:102.11.0+build1-0ubuntu0.22.04.1, 1:102.13.0+build1-0ubuntu0.22.04.1)
End-Date: 2023-07-11 06:25:07

Start-Date: 2023-07-11 10:37:02
Comman...

[Vladimir Petko (vpa1977)]

I have tried to reproduce the issue but had no luck so far. I could produce the graphical glitch, but no crash.

I wonder if it would be possible to provide a sample project and a list of plugins installed to reproduce the crash. Or produce a core dump by adding -XX:+CreateCoredumpOnCrash in eclipse.ini and enable core dumps in your system?

[Roger C-O (rogerco)]

Sorry, I fixed the problem for myself by simply not using Wayland, which seemed to be very buggy in lots of areas, not just this one.

I'm not going to try Wayland again I'm afraid. It may be there have been updates to Wayland since this first occurred, or maybe it has been fixed by one of the intervening Ubuntu updates. Perhaps the Eclipse update to 2023-09 helped.

In any event I've no intention of switching to Wayland again since that appears to be the cause of the problem.