Bug 535740 - [Webkit2] Tips browser crashes WebKit that powers Welcome view
Summary: [Webkit2] Tips browser crashes WebKit that powers Welcome view
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Leo Ufimtsev CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 535260
  Show dependency tree
 
Reported: 2018-06-09 11:09 EDT by Andreas Sewe CLA
Modified: 2018-06-29 15:31 EDT (History)
4 users (show)

See Also:


Attachments
Screenshot illustrating the situation (172.89 KB, image/png)
2018-06-09 11:15 EDT, Andreas Sewe CLA
no flags Details
JVM crash log (215.86 KB, text/x-log)
2018-06-09 13:15 EDT, Andreas Sewe CLA
no flags Details
Installed Ubuntu/Debian packages (323.68 KB, text/plain)
2018-06-12 07:05 EDT, Andreas Sewe CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Sewe CLA 2018-06-09 11:09:28 EDT
Noticed this testing the Photon RC3 Java EPP package under Ubuntu 8.4 on Wayland:

When I click through a couple of tips, Ubuntu's crash reporer (apport) pops up, telling me that Webkit crashed.

Interestingly, the browser widget within the Tips dialog seesm unaffected, but the Welcome view, which previously showed its usual content in the window behind the Tip of the Day dialog, is now blank.

From /var/log/apport.log:
ERROR: apport (pid 7421) Sat Jun  9 16:40:05 2018: wrote report /var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitWebProcess.1000.crash
ERROR: apport (pid 8710) Sat Jun  9 16:46:30 2018: called for pid 7723, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 8710) Sat Jun  9 16:46:30 2018: executable: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess (command line "/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 3 50")
ERROR: apport (pid 8710) Sat Jun  9 16:46:30 2018: debug: session gdbus call: (true,)
Comment 1 Andreas Sewe CLA 2018-06-09 11:15:34 EDT
Created attachment 274413 [details]
Screenshot illustrating the situation

I think I can refine my steps to reproduce:

- Click "Next tips" a couple of times until several "Unknown" processes have accumulated in the Ubuntu dock (Bug 535739).

  The Welcome view in the background looks still fine.

- Close the Tip of the Day dialog

  The Welcome view becomes blank (see screenshot)

- Close the Welcome view by clicking on the view's X.

  This *crashes* Eclipse

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f8c0ca2b9f9, pid=11961, tid=0x00007f8d03c30700
#
# JRE version: Java(TM) SE Runtime Environment (8.0_171-b11) (build 1.8.0_171-b11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.171-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libwayland-server.so.0+0x69f9]  wl_resource_post_event+0x99
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/sewe/Downloads/20180607-0625_eclipse-java-photon-RC3-linux.gtk.x86_64/eclipse/hs_err_pid11961.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Comment 2 Andrey Loskutov CLA 2018-06-09 12:33:30 EDT
Andreas, please attach hs_err_pid11961.log
Comment 3 Andreas Sewe CLA 2018-06-09 13:15:07 EDT
Created attachment 274416 [details]
JVM crash log
Comment 4 Leo Ufimtsev CLA 2018-06-11 09:47:40 EDT
(In reply to Andreas Sewe from comment #0)
> Noticed this testing the Photon RC3 Java EPP package under Ubuntu 8.4 on

I take it you mean ubuntu 18 rather than 8?

Might be because of:
532340 – [Gtk] Frozen UI opening a shell on Ubuntu 16.04 LTS, but works 17.10.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=532340

Can you list your gtk and webkit versions?
Comment 5 Leo Ufimtsev CLA 2018-06-11 09:53:37 EDT
btw, does this happen with x11 backend?

Can you post your webkitgtk and gtk lib versions?
Comment 6 Wim Jongman CLA 2018-06-12 06:41:44 EDT
Andreas you can do sudo dpkg -l > config.txt to list all your installed packages with versions.
Comment 7 Andreas Sewe CLA 2018-06-12 07:05:31 EDT
Created attachment 274441 [details]
Installed Ubuntu/Debian packages

(In reply to Wim Jongman from comment #6)
> Andreas you can do sudo dpkg -l > config.txt to list all your installed
> packages with versions.

Sure. config.txt attached.
Comment 8 Leo Ufimtsev CLA 2018-06-12 09:18:16 EDT
Thanks, you have webkit2.20 and gtk3.22 (which are the newest).

I'll try to reproduce the issue on my system. But I also have a suspicion as to what could be causing the crash.

Btw, are you able to test with a child eclipse?
If I can't reproduce the issue, would you be able to test with a gerrit patch to verify a bugfix?
Comment 9 Andreas Sewe CLA 2018-06-12 09:45:11 EDT
(In reply to Leo Ufimtsev from comment #8)
> Thanks, you have webkit2.20 and gtk3.22 (which are the newest).
> 
> I'll try to reproduce the issue on my system. But I also have a suspicion as
> to what could be causing the crash.

Would the contents of /var/crash/_usr_lib_x86_64-linux-gnu_webkit2gtk-4.0_WebKitWebProcess.1000.crash (mentioned in comment 0) help to confirm your suspicion? If so, I can attach crash report as well.
 
> Btw, are you able to test with a child eclipse?
> If I can't reproduce the issue, would you be able to test with a gerrit
> patch to verify a bugfix?

Yes, I am willing to test this with a runtime Eclipse, although I would need some pointers as to how to set up an Eclipse to compile (the necessary parts of) Platform. Last time I looked it was a bit more complicated than just installing the Platform project via Oomph. :-(
Comment 10 Leo Ufimtsev CLA 2018-06-29 15:31:35 EDT
Should be fixed by this guy:
https://git.eclipse.org/r/#/c/125270/

Please test with builds from next week & re-open with new stack trace if issue still occurs.