search

flathub / org.eclipse.Java

https://flathub.org/apps/details/org.eclipse.Java
4 stars 11 forks source link

[Wayland] Crash when clicking / moving the mouse in the Java editor #93

Closed Sollace closed 6 months ago

Sollace commented 7 months ago

Since updating the flatpak last night, Eclipse has begun to crash almost instantly after doing anything in the editor window. This morning I decided to run it in the console to try can capture the cause, and this is what I get.

I will note Eclipse has never been the most stable, on Windows or Linux, X11 or Wayland, but this seems out of the ordinary. The application is basically unusable in this state.

[sollace@Bismuth ~]$ flatpak run --branch=stable --arch=x86_64 --command=eclipse --file-forwarding org.eclipse.Java
Mar 31, 2024 12:01:19 PM org.apache.aries.spifly.BaseActivator log
INFO: Registered provider ch.qos.logback.classic.spi.LogbackServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle ch.qos.logback.classic
12:01:21.885 [Start Level: Equinox Container: 7ad1cc60-580c-4fed-a340-1b4fd34eabcc] DEBUG org.eclipse.jgit.internal.util.ShutdownHook -- register org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda$177/0x000000010025f270@1b2c02a6 with shutdown hook
12:01:21.885 [Start Level: Equinox Container: 7ad1cc60-580c-4fed-a340-1b4fd34eabcc] DEBUG org.eclipse.jgit.internal.util.ShutdownHook -- register org.eclipse.jgit.util.FS$FileStoreAttributes$$Lambda$177/0x000000010025f270@1b2c02a6 with shutdown hook
12:01:23.162 [main] DEBUG org.eclipse.m2e.core.internal.project.registry.ProjectRegistryRefreshJob -- Queued refresh request: *snip*

(Eclipse:26): Gdk-CRITICAL **: 12:01:51.220: gdk_window_create_gl_context: assertion 'GDK_IS_WINDOW (window)' failed
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f066858cb28, pid=26, tid=27
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.10+7 (17.0.10+7) (build 17.0.10+7)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (17.0.10+7, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libwebkit2gtk-4.1.so.0+0xd8cb28]
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/sollace/core.26)
#
# An error report file with more information is saved as:
# /home/sollace/hs_err_pid26.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
#

hs_err_pid27.log

Flatpak version:

Eclipse Foundation - The essential tools for any Java developer, including a
Java IDE, a Git client, XML Editor, Maven and Gradle integration

ID: org.eclipse.Java
Ref: app/org.eclipse.Java/x86_64/stable
Arch: x86_64
Branch: stable
Version: 4.31
License: EPL-2.0
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 395.3 MB
Runtime: org.gnome.Platform/x86_64/45
Sdk: org.gnome.Sdk/x86_64/45

Commit: be86925a4fc95d13c85535183c91e75df2728891678faf235d156f0fa5b7a933
Parent: aecc20258f0abcdba3538c412f472915a54178906155d98a42391396548c8ed1
Subject: Update changelog. (4cd365c1)
Date: 2024-03-10 09:34:14 +0000

System Version:

Operating System: Manjaro Linux 
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.6.19-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i9-11950H @ 2.60GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Sollace commented 7 months ago

Downgrading to commit 62f968a03f7ba326f8a4f83868a0ae1d159b41a6a55aba95c9a6541aadbb996d appears to fix the issue. Every version after that point exhibits the crash.

sudo flatpak update --commit=62f968a03f7ba326f8a4f83868a0ae1d159b41a6a55aba95c9a6541aadbb996d org.eclipse.Java
Mailaender commented 7 months ago

Can you try starting with the environment variable WEBKIT_DISABLE_COMPOSITING_MODE=1 or WEBKIT_DISABLE_DMABUF_RENDERER=1?

Sollace commented 7 months ago

Can you try starting with the environment variable WEBKIT_DISABLE_COMPOSITING_MODE=1 or WEBKIT_DISABLE_DMABUF_RENDERER=1?

On initial inspection that does seem to have helped. It could just be a fluke that it's deciding not to do it right now, so I'll continue to use it and come back once I'm more sure of the result.

Sollace commented 7 months ago

Another observation: Dragging windows to split the editor works slightly better with these options now, although I still need to hit [Return] to drop them.