[Wayland] Eclipse crashes on latest Ubuntu

[vogella]

Eclipse IDE frequently crashs for me on the latest Ubuntu release.

Eclipse SDK
Version: 2022-06 (4.24)
Build id: I20220512-1800
OS: Linux, v.5.15.0-27-generic, x86_64 / gtk 3.24.33, WebKit 2.36.0
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.1+12
Java version: 17.0.1

Error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f306673c3c4, pid=6457, tid=6458
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.1+12 (17.0.1+12) (build 17.0.1+12)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.1+12 (17.0.1+12, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libcairo.so.2+0x643c4]  cairo_region_num_rectangles+0x4
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /home/vogella/dev/eclipse-2022-05-05/eclipse/core.6457)
#
# An error report file with more information is saved as:
# /home/vogella/dev/eclipse-2022-05-05/eclipse/hs_err_pid6457.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[iloveeclipse]

Please attach /home/vogella/dev/eclipse-2022-05-05/eclipse/hs_err_pid6457.log and exact versions of gtk / cairo libraries.

[merks]

Note that the latest 17.x version is currently 17.0.3+7 though it's unlikely a bug in the JVM....

[mutatrum]

It seems this is the same crash. Eclipse is very unstable, it also exhibits jittery display in the Project Explorer, triggered by mouse moves. Crashes often when code assist popups Are shown. Behaviour was the same on JDK17.

hs_err_pid1156435.log

[iloveeclipse]

@mutatrum : Is the crash reproducible? If yes, please provide steps to reproduce. Looks like you are using wayland. Can you please switch to X11?

[vogella]

/home/vogella/dev/eclipse-2022-05-05/eclipse/hs_err_pid6457.log

Sorry was on holiday.

Cairo library:

vogella@Scyth:/usr/lib$ dpkg -l | grep cairo
ii  gtk2-engines-murrine:amd64                 0.98.2-3build2                          amd64        cairo-based gtk+-2.0 theme engine
ii  libcairo-gobject-perl:amd64                1.005-3build1                           amd64        integrate Cairo into the Glib type system in Perl
ii  libcairo-gobject2:amd64                    1.16.0-5ubuntu2                         amd64        Cairo 2D vector graphics library (GObject library)
ii  libcairo-perl:amd64                        1.109-2build1                           amd64        Perl interface to the Cairo graphics library
ii  libcairo-script-interpreter2:amd64         1.16.0-5ubuntu2                         amd64        Cairo 2D vector graphics library (script interpreter)
ii  libcairo2:amd64                            1.16.0-5ubuntu2                         amd64        Cairo 2D vector graphics library
ii  libcairomm-1.0-1v5:amd64                   1.12.2-4build3                          amd64        C++ wrappers for Cairo (shared libraries)
ii  libdecor-0-plugin-1-cairo:amd64            0.1.0-3build1                           amd64        default decoration plugin
ii  libpangocairo-1.0-0:amd64                  1.50.6+ds-2                             amd64        Layout and rendering of internationalized text
ii  libpixman-1-0:amd64                        0.40.0-1build4                          amd64        pixel-manipulation library for X and cairo
ii  python3-cairo:amd64                        1.20.1-3build1                          amd64        Python3 bindings for the Cairo vector graphics library
ii  python3-gi-cairo                           3.42.0-3build1                          amd64        Python 3 Cairo bindings for the GObject library

Here is the log (can't attach all was it is too long)

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f306673c3c4, pid=6457, tid=6458
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.1+12 (17.0.1+12) (build 17.0.1+12)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.1+12 (17.0.1+12, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libcairo.so.2+0x643c4]  cairo_region_num_rectangles+0x4
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /home/vogella/dev/eclipse-2022-05-05/eclipse/core.6457)
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# 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: -Dosgi.requiredJavaVersion=11 -Dosgi.dataAreaRequiresExplicitInit=true -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Xms256m -Xmx2048m --add-modules=ALL-SYSTEM /home/vogella/dev/eclipse-2022-05-05/eclipse//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar -os linux -ws gtk -arch x86_64 -showsplash -launcher /home/vogella/dev/eclipse-2022-05-05/eclipse/eclipse -name Eclipse --launcher.library /home/vogella/dev/eclipse-2022-05-05/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.2.500.v20220509-0833/eclipse_11701.so -startup /home/vogella/dev/eclipse-2022-05-05/eclipse//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar --launcher.appendVmargs -exitdata b -vm /home/vogella/.sdkman/candidates/java/current/bin/java -vmargs -Dosgi.requiredJavaVersion=11 -Dosgi.dataAreaRequiresExplicitInit=true -Dorg.eclipse.swt.graphics.Resource.reportNonDisposed=true -Xms256m -Xmx2048m --add-modules=ALL-SYSTEM -jar /home/vogella/dev/eclipse-2022-05-05/eclipse//plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar

Host: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz, 8 cores, 31G, Ubuntu 22.04 LTS
Time: Sat May 21 10:21:01 2022 CEST elapsed time: 43.768422 seconds (0d 0h 0m 43s)

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

Current thread (0x00007f30b0024950):  JavaThread "main" [_thread_in_native, id=6458, stack(0x00007f30b62d8000,0x00007f30b63d8000)]

Stack: [0x00007f30b62d8000,0x00007f30b63d8000],  sp=0x00007f30b63d4f58,  free space=1011k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [libcairo.so.2+0x643c4]  cairo_region_num_rectangles+0x4

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J 2780  org.eclipse.swt.internal.gtk3.GTK3.gtk_main_do_event(J)V (0 bytes) @ 0x00007f30a10b7069 [0x00007f30a10b7020+0x0000000000000049]
J 10964 c2 org.eclipse.swt.widgets.Display.eventProc(JJ)J (212 bytes) @ 0x00007f30a146c3b8 [0x00007f30a146c300+0x00000000000000b8]
v  ~StubRoutines::call_stub
J 2769  org.eclipse.swt.internal.gtk3.GTK3.gtk_main_iteration_do(Z)Z (0 bytes) @ 0x00007f30a10b6469 [0x00007f30a10b6420+0x0000000000000049]
J 12276 c1 org.eclipse.swt.widgets.Display.readAndDispatch()Z (88 bytes) @ 0x00007f309ae9533c [0x00007f309ae951c0+0x000000000000017c]
j  org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run()V+564
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$246+0x0000000800dfd588.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@17.0.1
j  jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+133 java.base@17.0.1
j  jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+6 java.base@17.0.1
j  java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+59 java.base@17.0.1
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: 0x0000000000000004

0x00007f30b63d4f88:   00007fct 20 2021 12:00:24 by "" with gcc 7.5.0

END.

[vogella]

Way to reproduce:

• Open Welcome Screen
• Click on Migrate
• Click on Eclipse Platform

Bye bye Eclipse

[iloveeclipse]

@vogella : are you also using wayland? If yes, can you please switch to X11 & check if that will still crash?

[vogella]

@nnemkin @akurtakov @niraj-modi FYI this bugs makes Eclipse impossible to use with latest Ubuntu.

[vogella]

@vogella : are you also using wayland? If yes, can you please switch to X11 & check if that will still crash?

Works fine with X11. Still a critial bug as Ubuntus deault is Wayland.

[niraj-modi]

Couple of queries:
Is it a regression in 4.24 M3 ?
Also is it specific to Java17 ?

@sravanlakkimsetti @joel-majano
Any idea here ?

[akurtakov]

Is your ubuntu fully uptodate?

[heike2718]

Same on Debian 10

Eclipse crashes frequently and unpredictably under Debian 10. It could not be reproduced yet. In a forum there was a tip to start Eclipse with the command line option -Djdk.gtk.version=2. But that does not help. Eclipse is therefore no longer usable under Debian, which is very regrettable.

Please check one of the crash-reports:

hs_err_pid14497.log

Operating System: Debian GNU/Linux 10 (buster)
Kernel: Linux 4.19.0-20-amd64

Output of "Help->About Eclipse-> "Copy build Id informatin to clipboard":

Eclipse IDE for Java Developers (includes Incubating components)
Version: 2022-03 (4.23.0)
Build id: 20220310-1457
OS: Linux, v.4.19.0-20-amd64, x86_64 / gtk 3.24.5
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.2+8
Java version: 17.0.2

My Eclipse is running with openjdk version "11.0.15" 2022-04-19.

[sravanlakkimsetti]

Same on Debian 10

Eclipse crashes frequently and unpredictably under Debian 10. It could not be reproduced yet. In a forum there was a tip to start Eclipse with the command line option -Djdk.gtk.version=2. But that does not help. Eclipse is therefore no longer usable under Debian, which is very regrettable.

Please check one of the crash-reports:

hs_err_pid14497.log

Operating System: Debian GNU/Linux 10 (buster) Kernel: Linux 4.19.0-20-amd64

This is a different crash related to webkit. Please open this as a separate issue.

[heike2718]

@sravanlakkimsetti

OK, sorry.

I did open a new issue.

[sravanlakkimsetti]

I tried to reproduce this problem on Ubuntu 22.04
Eclipse SDK
Version: 2022-06 (4.24)
Build id: I20220525-1800
OS: Linux, v.5.15.0-33-generic, x86_64 / gtk 3.24.33, WebKit 2.36.2
Java vendor: Eclipse Adoptium
Java runtime version: 17.0.3+7
Java version: 17.0.3

Cannot reproduce this problem. Tried using gnome and Ubuntu desktop environments.

From the description I think the help web app is not getting launched.

[iloveeclipse]

Cannot reproduce this problem

@sravanlakkimsetti : have you tried with Wayland or X11? It crashes on Wayland only, at least for Lars, see above.

[sravanlakkimsetti]

I used wayland

[iloveeclipse]

Note, that there are few bugs reporting same crash in cairo_region_num_rectangles on Wayland for Eclipse like https://bugs.openjdk.java.net/browse/JDK-8244794, they are also on wayland (see loaded libraries section).

I wonder if there is some additional precondition for the crash.

[akurtakov]

I have some feeling it could be even driver specific issue.

[mutatrum]

For me It started on Ubuntu 21.10/JDK 17.0.3+7, Eclipse 4.23.

hs_err_pid1028125.log

It also occured on 4.22M3:

hs_err_pid9088.log

The steps above (Welcome -> Migrate -> Eclipse platform) seem to trigger it. Other than that, I have no clear reproduction steps, but the first sign is flickering of the text in the project view. Flickering is triggered by cursor and mouse movement, however, the flickering is not there on startup. The use of a console or terminal view seems to initiate the flickering.

One side-effect I sometimes see: after a refactoring, the edit pane is briefly showing colored diagonal lines.

Screenshot of the edit pane, this flashes for a few 100ms, after a refactor:

Not sure if this is related, but I can't remember this seeing before.

[vogella]

Is your ubuntu fully uptodate?

Yes

[mutatrum]

Is your ubuntu fully uptodate?

Yes. Ubuntu 22.04, gnome 42.1, libgtk-3-0:amd64 3.24.33-1ubuntu2

[SyntevoAlex]

I tried to reproduce.
Installed fresh Ubuntu 22.04, Eclipse I20220531-0600.
Clicked various buttons for a few minutes, seen no problems.

[SyntevoAlex]

For those who can reproduce it:

1. Add -XX:+CreateCoredumpOnCrash to your eclipse.ini, for example after -Xmx2048m.
2. Run this command to enable core dumps in your Linux:
   $ ulimit -c unlimited
3. Reproduce crash
4. Find the core dump (look in ~ and Eclipse dir)
5. Compress (7z is quite good) and share the dump.

I never tried these steps myself (with Eclipse), hopefully it will work as intended.

[SyntevoAlex]

Note that the dump will likely contain all memory of eclipse's process, which may include sources you opened, password, etc. So it's a good idea to reproduce with a clean workspace.

[AmiDavidW]

I got a similar issue with Eclipse 2022-03 on Ubuntu 2204 Jammy Jellyfish.

After one or more class, method, or variable renamings, the Java editor window becomes the same as the screenshot of the post of mutatrum above for a couple of seconds. Then, the memory usage of Eclipse starts growing until Eclipse crashes.

Didn't observe the same behavior on Ubuntu 2004 Focal Fossa.

[SyntevoAlex]

@AmiDavidW could you please follow steps from #158 (comment) to capture a core dump?

[4javier]

The issue originally reported on this ticket has nothing to do with current problem we're all facing.
I don't know why, but at some point people started to use this bugtrack to report a different problem as in a cargo cult.
I've been tricked to do that too, before realizing the mistake.
Btw, the bug is absolutely not limited to Ubuntu, it's present in any system running Wayland and an Eclipse build linking almost every "recent" version of libwebkit2gtk.
You'll find at least a couple of other tickets opened explicitly for this issue, on webkit bugtracker and on eclipse one.

[danthe1st]

@BrotherPatrix As far as I know the issue should be fixed already and that fix would be included in 2024-06. See this comment for example. See this for installing a release candidate if you want to test it.

[BrotherPatrix]

The issue originally reported on this ticket has nothing to do with current problem we're all facing. I don't know why, but at some point people started to use this bugtrack to report a different problem as in a cargo cult. I've been tricked to do that too, before realizing the mistake.

Original issue involved Ubuntu, then people realized it's something more specific and agrees which I assume is the reason why this is still open. I don't see a mistake here.

@BrotherPatrix As far as I know the issue should be fixed already and that fix would be included in 2024-06. See this comment for example. See this for installing a release candidate if you want to test it.

Cool, the version I downloaded today was 2024-03 so maybe it's just around the corner. Will be looking forward to it. Thanks for the heads up!

[4javier]

The original issue has nothing to do with the current one.
It was targeting libcairo, not libwekit2gtk.
I already tried 2024-06 and nothing changed.
Hope you'll have better luck.

[HannesWell]

Not sure what the deal is here

As a general remarks, even though the state of the original issue seems to be not absolutely clear:
SWT just like Eclipse in total is an Open-Source project developed by a community of different people with different interests. And while it is in the general interest of us all to keep SWT and Eclipse in good shape there is no team whose only task is to fix user's issues. It is of course relatable that this issue is annoying for you, but unfortunately it looks like no one of the active contributors is currently dedicated to work on this particular issue. Please also see: https://github.com/eclipse-platform/#community
But if you are interested in contributing to a quality solution it would be of course more than welcome.

[BrotherPatrix]

Not sure what the deal is here

... it is in the general interest of us all to keep SWT and Eclipse in good shape there is no team whose only task is to fix user's issues. It is of course relatable that this issue is annoying for you, but unfortunately it looks like no one of the active contributors is currently dedicated to work on this particular issue ...

So basically what you are saying is that you don't see this as an important issue so you're going to work on something you think is important. I might not have a good demographic about the situation, like how many users are affected because of this, and judging by the number of comments here, you are probably right, also a lot of people that probably don't like Wayland and would like to stick to X11. I'm just stating my two cents, that this is bad not only for me, I am happy though that I did find a temporary solution. That's it!

... Please also see: https://github.com/eclipse-platform/#community But if you are interested in contributing to a quality solution it would be of course more than welcome.

But this?! And I want to emphasize on the contributing to a quality solution statement. Are you telling me that this issue requires a quality fix? Listen, I do programming, and I can understand the technical complications that can arise
in certain situations like @4javier's mentions, but I'm coming here with the intention of stating my case, giving information on where this can also happen, and I'm sorry I'm not helpful but with first impressions I can only say this is bad. I don't like IntelliJ, I don't like NetBeans, I don't agree with VSCode on their approach on Java and I don't have the time to try and configure NeoVim or Emacs and I decided to stick with Eclipse because it offers everything I need in a stable way.

Here is my reality:
Wayland is going to be default on most Linux distributions and if Eclipse does not work correctly under this WM, then I see this as a critical bug and people don't care about the technicality, they just want it to work.

[jmreymond]

Other Eclipse-based software, such as Talend Open Studio, are affected by the bug and cannot run on Wayland.

[4javier]

Wayland has more than an issue with libwebkit2gtk.
Even some official Gnome packages like Evolution had to disable hardware acceleration on wayland to work.
Real ticket to correctly track the issue is this one
https://bugs.webkit.org/show_bug.cgi?id=271477

[michael-schnell]

It's sad, but after ~20 years using Eclipse as my main IDE, I finally moved to IntelliJ Idea because of this bug.

[4javier]

Good news!
Today I upgraded wayland to version 1.23.0 and I can confirm that Eclipse version 4.32M1 and SpringToolSuite snapshot 4.23 (based on Ecplise 4.32 too) are back working smoothly, at first sight.
Eclipse 4.31 and tools based on it still show the bug.

Just to clarify Eclipse 4.32 is already in RC1 and should reach stable soon.

[HannesWell]

Not sure what the deal is here

... it is in the general interest of us all to keep SWT and Eclipse in good shape there is no team whose only task is to fix user's issues. It is of course relatable that this issue is annoying for you, but unfortunately it looks like no one of the active contributors is currently dedicated to work on this particular issue ...

So basically what you are saying is that you don't see this as an important issue so you're going to work on something you think is important. I might not have a good demographic about the situation, like how many users are affected because of this, and judging by the number of comments here, you are probably right, also a lot of people that probably don't like Wayland and would like to stick to X11. I'm just stating my two cents, that this is bad not only for me, I am happy though that I did find a temporary solution. That's it!

It's not that I don't think it is important, but at least I personally can't work on this since I lack the knowledge about the SWT native part especially on Wayland because I'm mainly on Windows. And for others it might be the same or maybe they have things to do that are more important for them. As said we are a community and we cannot force anybody to work on any specific topic. Maybe one day some employer instructs an employee to work on this or somebody hires a contractor or someone whose capable just fixes it because it's annoying to that person:
https://github.com/eclipse-platform/#community

Since you asked why this is not resolved I just wanted to explain the situation.

... Please also see: https://github.com/eclipse-platform/#community But if you are interested in contributing to a quality solution it would be of course more than welcome.

But this?! And I want to emphasize on the contributing to a quality solution statement. Are you telling me that this issue requires a quality fix?

This statement's intend was to encourage you or anyone else interested in this to contribute to a solution that solves the issue, ideally in a sustainable and durable way (as everyone is interested in such solutions). If this was ambiguous, I'm sorry.

[HannesWell]

Good news! Today I upgraded wayland to version 1.23.0 and I can confirm that Eclipse version 4.32M1 and SpringToolSuite snapshot 4.23 (based on Ecplise 4.32 too) are back working smoothly, at first sight. Eclipse 4.31 and tools based on it still show the bug.

Thank you for reporting back good news.
@vogella or anybody else can you confirm 4.32 RC works fine for you?

Just to clarify Eclipse 4.32 is already in RC1 and should reach stable soon.

Yes the 4.32 release general availability is planned for Wednesday next week, June 12th:
https://calendar.google.com/calendar/embed?src=prfk26fdmpru1mptlb06p0jh4s%40group.calendar.google.com

But everyone can already test RC1 from:
https://www.eclipse.org/downloads/packages/release/2024-06
And RC2 should be available by the end of this week.

[4javier]

@HannesWell
I preferred to not be too much precise with info about RC availability because the issue is widespread even among less "techie" people, and maybe it's betterto to not suggest the use of unstable versions to everyone.
About vogella, unfortunately he's the author of the original issue, that's not related with the one we're discussing now, and it seems to me he didn't participate in discussions about the current one, so I don't think he can do any test.
Thanks for your support in the ticket!

[vogella]

@HannesWell we moved to the I-Build with one of our Ubuntu installations in which the Eclipse IDE constantly crashes whenever we try to open a JS or css file. So far so good, we did not had a crash for 10 minutes now. A new record on this machine.

[4javier]

@vogella
sounds like another different issue, tho.
Are you using WildWebDeveloper or WTP for web development?

[vogella]

@vogella sounds like another different issue, tho. Are you using WildWebDeveloper or WTP for web development?

At least it does not happen anymore with the latest I-build. I think we saw this issue with and without WWD but as it does no happen anymore, I cannot be 100% sure.

[danthe1st]

Good news! Today I upgraded wayland to version 1.23.0 and I can confirm that Eclipse version 4.32M1 and SpringToolSuite snapshot 4.23 (based on Ecplise 4.32 too) are back working smoothly, at first sight. Eclipse 4.31 and tools based on it still show the bug.

Thank you for reporting back good news. vogella or anybody else can you confirm 4.32 RC works fine for you?

Just to clarify Eclipse 4.32 is already in RC1 and should reach stable soon.

Yes the 4.32 release general availability is planned for Wednesday next week, June 12th: https://calendar.google.com/calendar/embed?src=prfk26fdmpru1mptlb06p0jh4s%40group.calendar.google.com

But everyone can already test RC1 from: https://www.eclipse.org/downloads/packages/release/2024-06 And RC2 should be available by the end of this week.

For me it works with the 2024-06 release candidate while 2024-03 crashes with the libwebkit2gtk message.

[4javier]

@danthe1st
Which version of wayland package, and what distro?

[danthe1st]

@danthe1st Which version of wayland package, and what distro?

I am using Ubuntu 24.04 LTS x86_64 on GNOME 46.0 with mutter 46.0-1ubuntu9

EDIT: dpkg --list|grep libwebkit gives me the following output:

ii  libwebkit2gtk-4.1-0:amd64                      2.44.2-0ubuntu0.24.04.1                  amd64        Web content engine library for GTK
ii  libwebkitgtk-6.0-4:amd64                       2.44.2-0ubuntu0.24.04.1                  amd64        Web content engine library for GTK

[adisandro]

I'm hitting this problem even on Eclipse 2024-06 RC1, and I have to use the GDK_BACKEND=x11 workaround.
I'm on Debian Sid, Wayland 1.22.0, libwebkitgtk 2.45.3.

[gustabart]

I downloaded the last Eclipse IDE 2024-06 yesterday (Version 4.32.0).
The problem was resolved. It works correctly on wayland.

➜  ~ dpkg --list|grep libwebkit
ii  libwebkit2gtk-4.0-37:amd64                 2.44.2-0ubuntu0.22.04.1                 amd64        Web content engine library for GTK
➜  ~ dpkg -l | grep wayland    

ii  libwayland-client0:amd64                   1.20.0-1ubuntu0.1                       amd64        wayland compositor infrastructure - client library

[dmatej]

The RC1 is crashing too, but it seems from different reason (I have same lib versions as @gustabart ). Also sometimes context menus are lagging for a minute, but that happens on Thunderbird too, so maybe that is something between Wayland and GTK. I also noticed that I was able to restart kwin when running X11 with kwin_x11 --replace & but on Wayland when I run kwin_wayland --replace & everything crashes.
I am downloading the 2024-06 right now.

[cipianpascu]

Sadly, after upgrading to Ubuntu 24.04 & Eclipse 2024-06, the Wayland session restarts without any warning,

[dmatej]

Sadly, after upgrading to Ubuntu 24.04 & Eclipse 2024-06, the Wayland session restarts without any warning,

I can see it on the Kubuntu 22.04.4 too with the latest final Eclipse IDE version:

• On start, Eclipse freezes for long 2-10 minutes, then finally starts. The CPU load is around 400% in htop and the window title is set to Eclipse IDE Launcher (Not Responding)
• After some work (5 minutes to 2 days uptime), Eclipse crashes without any log. Just pops out the crash report with JVM options etc. It seems to me the less I work with that the more probable is the crash but I am not sure with that.
• Yesterday crashed all applications in the Wayland session; Question: Is it really possible that one application can crash the whole system UI?

With export GDK_BACKEND=x11 it starts in 5 seconds even with the load produced by the second workspace. Currently I don't know yet how long uptime it can take. But it doesn't seem the issue is resolved.

[danthe1st]

• On start, Eclipse freezes for long 2-10 minutes, then finally starts. The CPU load is around 400% in htop and the window title is set to Eclipse IDE Launcher (Not Responding)

I had a similar issue with the latest release (startup takes some time while resolving OSGi modules) though reinstalling Eclipse worked for me. You can try using the -clean option to fix that.

• After some work (5 minutes to 2 days uptime), Eclipse crashes without any log. Just pops out the crash report with JVM options etc.

Is that the same error as above?

Is it really possible that one application can crash the whole system UI?

This may be a GTk bug IIRC.

[HannesWell]

@HannesWell we moved to the I-Build with one of our Ubuntu installations in which the Eclipse IDE constantly crashes whenever we try to open a JS or css file. So far so good, we did not had a crash for 10 minutes now. A new record on this machine.

@vogella can we assume that the original issue has been resolved and can close this one?
I'm not an expert for for Wayland, but if there are other issues with SWT on Wayland it would be easier to resolve if there are dedicated issues instead of one large 'SWT Wayland problems' issue.

[vogella]

Eclipse runs fine for me on latest Ubuntu. Feel free to close

[HannesWell]

Eclipse runs fine for me on latest Ubuntu. Feel free to close

Thanks for the update. Ok, closing this.
Everyone with problems under Linux using Wayland, please create dedicated bug reports for them with as detailed as possible steps to reproduce. And please make sure there is not already an issue for that exact issue. If so please check if you can help to resolve it.

[dpetroff]

I ended up here recently after searching the very generic error message at the top. It's worth emphasising for anyone else that gets here now that if you're still getting the issue with eclipse, it's worth trying to apt dist-upgrade first since a similar error may pop up anyway with an outdated wayland version even if your eclipse is up to date. I'm unlucky enough to be running an Ubuntu-based corporate home-brew distro that has been stripped of the standard auto-update features, so it was necessary to do this manually to avoid getting the error.