FS#75453 - [webkit2gtk] 2.36.5-1 Eclipse crashes on gnome
Attached to Project:
Arch Linux
Opened by Eduardo Frazão (EduFrazao) - Friday, 29 July 2022, 13:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 01 August 2022, 23:06 GMT
Opened by Eduardo Frazão (EduFrazao) - Friday, 29 July 2022, 13:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Monday, 01 August 2022, 23:06 GMT
|
Details
After upgrade to from webkit2gtk 2.36.4-2 to 2.36.5-1, few
seconds after start Eclipse IDE, Gnome says that UI stops to
respond and closes it.
No error reported on console, dmesg or java crashes reports. After downgrade package to 2.36.4-2, everything works fine. Tested with two versions of Eclipse and Java JRE. Exactly same behavior. Downgrade command: pacman -U file:///var/cache/pacman/pkg/webkit2gtk-2.36.4-2-x86_64.pkg.tar.zst Additional info: * package version(s) Java jdk-17.0.3+7 Eclipse: 2022-03 (4.23.0) - Build id: 20220310-1457 Gnome: 42.3 Kernel: 5.18.14-arch1-1 Mesa: 22.1.4-1 * config and/or log files etc. Machine config: Ryzen 9 5900x // 64GB RAM // AMD 5700XT GPU * link to upstream bug report, if any Steps to reproduce: Perform a full system update (pacman -Syu) After upgrade webkit2gtk to version 2.36.5-1, Downloads Eclipse IDE from (https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/2022-06/R/eclipse-jee-2022-06-R-linux-gtk-x86_64.tar.gz), unpack it and execute "eclipse" binary. This package ships with their own JDK. You can use it, or use JDK avaliable on Arch Repos, like jdk11-openjdk. Nothing changes. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Monday, 01 August 2022, 23:06 GMT
Reason for closing: Fixed
Additional comments about closing: webkit2gtk 2.36.5-2
Monday, 01 August 2022, 23:06 GMT
Reason for closing: Fixed
Additional comments about closing: webkit2gtk 2.36.5-2
From my experiments, the problem occurs as soon as you try to use the internal web browser or if you hover (e.g., for Javadoc), which again uses the WebKit component for rendering the HTML.
That's the only reason it crashes. Of course, opening a Java editor and moving the mouse over the code is almost enough to have the crash since it almost immediately triggers hovering.
This renders the Eclipse Java IDE essentially unusable.
I support to increase the priority of this bug.
Some logs
https://cpaste.org/?b397069334fa51f6#8SoYBtD4haar6YoXgu4JifWrJGznb2KPUrAfSM4RvmfD
https://cpaste.org/?dc4f56021bd226ec#3rHnometDY2Dr5UmvsgDYi2fYgqXBqhHM4QKogDxf7r2
Even just trying to edit a scss file triggers core dump.
I mistakenly reported the bug to WildWebDeveloper tracker thinking the plugin was the culprit.
It looks like the crash is due to this failed assertion: https://github.com/WebKit/WebKit/blob/webkitgtk/2.36/Source/WebKit/UIProcess/WebsiteData/WebsiteDataStore.cpp#L101
While the files mentioned in the trace haven't been changed recently, the semantics of isMainThread have indeed been changed between 2.36.4 and 2.36.5: see https://github.com/WebKit/WebKit/commit/50d7bfe855ca043cc72ec09b3d3d75100015101b#r78597817 and https://github.com/WebKit/WebKit/commit/6a1445596f978d93f7eafe50629115d896d3a22b
I suspect this is either an upstream bug (the semantics of isMainThread are still off), or a bug in Eclipse, i.e., SWT is calling webkitgtk2 functions in a manner that is not thread-safe, but allowed by the previous (wrong) isMainThread semantics.
It means that it's not included as a package in any official repo. It's just in AUR or in third party repo.
@Toolybird
Don't worry. I was in contact with an official Eclipse plugin dev, and he opened the ticket for the right Eclipse component
https://github.com/eclipse-platform/eclipse.platform.swt/issues/281
I don't think this is a webkit bug because, just to say one, devhelp works flawlessy linking the same version.
After downgrading package to 2.36.4-2, everything works again.
https://github.com/WebKit/WebKit/pull/2904
Here is this same issue on webkit website: https://bugs.webkit.org/show_bug.cgi?id=243401
P.S. Thank you, it is fixed now. Please ignore my stupid request to re-open, my pacman had a slow updateMirror