After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 733707 - WebkitWebProcess crashing navigating away from ogg video file
WebkitWebProcess crashing navigating away from ogg video file
Status: RESOLVED NOTGNOME
Product: epiphany
Classification: Core
Component: Backend
3.10.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-07-25 03:35 UTC by Matt Watson
Modified: 2014-07-28 20:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gjs file and two tiny html pages to crash webkit (424.17 KB, application/gzip)
2014-07-25 03:35 UTC, Matt Watson
Details

Description Matt Watson 2014-07-25 03:35:28 UTC
Created attachment 281654 [details]
gjs file and two tiny html pages to crash webkit

A crash in webkitgtk3. Didn't see any way to file directly against webkitgtk, so filing against epiphany.

To reproduce
 - load a page with a ogg video in a html5 video element
 - load another page
 - WebkitWebProcess will crash

Attaching a minimal test case using webkitgtk3 directly. To run extract and cd webkit_crash run gjs browser.js, this will load the video page, click the link to load a second page and crash webkit. Sorry about the cumbersome test case, but only seems to crash when loading a second page after the video page.

Alternately in epiphany
 - open http://www.w3schools.com/html/tryit.asp?filename=tryhtml_video_html5_4
 - open http://google.com
 - "Oops something has gone wrong"

Tested on Fedora 20. May affect more than ogg, but doesn't seem to be all video formats.

Here's the backtrace that gets printed...

1   0xb76130a1 /lib/libjavascriptcoregtk-3.0.so.0(WTFCrash+0x21) [0xb76130a1]
2   0xb761a8c8 /lib/libjavascriptcoregtk-3.0.so.0(_ZN3WTF10fastMallocEj+0x298) [0xb761a8c8]
3   0xb5cd5755 /lib/libwebkit2gtk-3.0.so.25(+0xd71755) [0xb5cd5755]
4   0xb5cd5812 /lib/libwebkit2gtk-3.0.so.25(+0xd71812) [0xb5cd5812]
5   0xb5cd23a1 /lib/libwebkit2gtk-3.0.so.25(+0xd6e3a1) [0xb5cd23a1]
6   0xb5cd2463 /lib/libwebkit2gtk-3.0.so.25(+0xd6e463) [0xb5cd2463]
7   0xb5ce4c62 /lib/libwebkit2gtk-3.0.so.25(+0xd80c62) [0xb5ce4c62]
8   0xb5ce4e37 /lib/libwebkit2gtk-3.0.so.25(+0xd80e37) [0xb5ce4e37]
9   0xb5ce4905 /lib/libwebkit2gtk-3.0.so.25(+0xd80905) [0xb5ce4905]
10  0xb5ce4aeb /lib/libwebkit2gtk-3.0.so.25(+0xd80aeb) [0xb5ce4aeb]
11  0xb5ce4e37 /lib/libwebkit2gtk-3.0.so.25(+0xd80e37) [0xb5ce4e37]
12  0xb5ce4905 /lib/libwebkit2gtk-3.0.so.25(+0xd80905) [0xb5ce4905]
13  0xb5ce4aeb /lib/libwebkit2gtk-3.0.so.25(+0xd80aeb) [0xb5ce4aeb]
14  0xb5ce4e37 /lib/libwebkit2gtk-3.0.so.25(+0xd80e37) [0xb5ce4e37]
15  0xb5ce4905 /lib/libwebkit2gtk-3.0.so.25(+0xd80905) [0xb5ce4905]
16  0xb5ce4aeb /lib/libwebkit2gtk-3.0.so.25(+0xd80aeb) [0xb5ce4aeb]
17  0xb5ce4e37 /lib/libwebkit2gtk-3.0.so.25(+0xd80e37) [0xb5ce4e37]
18  0xb5ce4905 /lib/libwebkit2gtk-3.0.so.25(+0xd80905) [0xb5ce4905]
19  0xb5ce4a19 /lib/libwebkit2gtk-3.0.so.25(+0xd80a19) [0xb5ce4a19]
20  0xb52f9c2f /lib/libwebkit2gtk-3.0.so.25(+0x395c2f) [0xb52f9c2f]
21  0xb52fa132 /lib/libwebkit2gtk-3.0.so.25(+0x396132) [0xb52fa132]
22  0xb52fa1f5 /lib/libwebkit2gtk-3.0.so.25(+0x3961f5) [0xb52fa1f5]
23  0xb52fa2bc /lib/libwebkit2gtk-3.0.so.25(+0x3962bc) [0xb52fa2bc]
Comment 1 Michael Catanzaro 2014-07-25 13:41:33 UTC
Thanks for the detailed reproducer. Unfortunately it doesn't crash for me with WebKit 2.2.7 on F20. :/  It's possible this bug only occurs for 32 bit builds, but most WebKit developers have 64 bit computers.

For the best odds at getting this bug resolved:

* Make sure you've installed the (big) package webkitgtk3-debuginfo
* Get a real stack trace following the instructions at [1] (ignore the section "Obtaining a stack trace using GDB for a program that is not yet running" -- you'll need to either use a core dump or else attach gdb to the WebKitWebProcess)
* File this over on https://bugs.webkit.org/ instead
* Post again here with a link to the new bug report

[1] https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details

When reporting the WebKit bug, be sure to include '[GTK]' in the summary and use the 'gtk' keyword. Thanks!
Comment 2 Matt Watson 2014-07-25 21:09:41 UTC
Thanks! I'll do that this weekend.

I was on a fresh 32 bit VM I had just made in virtual box from the fedora ISO
Comment 3 Matt Watson 2014-07-28 20:41:19 UTC
Alright, posted over on webkit, put the full stack trace over there.
https://bugs.webkit.org/show_bug.cgi?id=135348