GNOME Bugzilla – Bug 777947
Opening a tab with Ctrl+left Mousebutton crashs existing and new tab
Last modified: 2017-02-05 22:18:33 UTC
Created attachment 344565 [details] current installed packages Hello! Since around two weeks I'm suffering a serious bug in Epiphany. Every time I open a new tab from an existing tab with Ctrl+left Mousebutton the existing tab and the new tab crashes. It possible to reload both tabs successfully with Ctrl+r, but input in a textfield in the first tab will be lost. Preconditions: X11, not tested on Wayland yet. Reproduce: 1. Open a page with a link to another one 2. Ctrl+left Mousebutton on the link 3. crash of both tabs I know that this bug is possibly not directly inside Epiphany and maybe in the graphics stack, at least Epiphany is here starting point. I marked this bug a critical, because tabs are currently not usable anymore if not opend manually by Ctrl+t. Thank you Further notes: Midori (with Gtk3 and WebKit2Gtk) is not affected.
(In reply to Peter from comment #0) > I know that this bug is possibly not directly inside Epiphany and maybe in > the graphics stack, at least Epiphany is here starting point. I marked this > bug a critical, because tabs are currently not usable anymore if not opend > manually by Ctrl+t. Yup, that sounds pretty bad. It doesn't happen for me, though. Could you get a stacktrace? Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance! It miiight turn out to be https://bugs.webkit.org/show_bug.cgi?id=167296, but no way to know without a stacktrace.
Created attachment 344567 [details] stacktrace from journalctl -rb you can see that intel driver is involved
this is from dmesg: [21820.910968] WebKitWebProces[10709]: segfault at 0 ip 00007f6a5d3d9da5 sp 00007f69f59fdfd8 error 4 in libc-2.24.so[7f6a5d356000+195000] I will know switch to Wayland and try to reproduce it there.
This bug seems not to affect affect Wayland :)
We're going to need a better stacktrace with debug info to see what's going on. Since you have systemd-coredump enabled, coredumpctl will make that very easy to get once you've installed appropriate debuginfo.
I cannot give you an ETA for a full stacktrace, but I will try to use some free time this week for it :)
I dunno what distro you're using or how hard it makes it to get a stacktrace, but this should be a 5-10 minute task. You just need to install debuginfo for mesa and webkitgtk.
Archlinux, so I have to compile that stuff. But I'm glad to hear, that mesa and webkitgtk are enough.
[ 16%] Building CXX object Source/JavaScriptCore/CMakeFiles/JavaScriptCore.dir/runtime/TypeSet.cpp.o [ 16%] Building CXX object Source/JavaScriptCore/CMakeFiles/JavaScriptCore.dir/runtime/TypedArrayController.cpp.o [ 16%] Building CXX object Source/JavaScriptCore/CMakeFiles/JavaScriptCore.dir/runtime/TypedArrayType.cpp.o ... I'm compiling WebKit2Gtk now for around one hour, please bear with me ;)
[100%] Linking CXX executable ../../bin/WebKitPluginProcess2 Running gtkdoc-fixxref html/WebKitDOMDOMWindow.html:48: warning: no link for: 'WebKitDOMDOMApplicationCache' -> (<span class="type">WebKitDOMDOMApplicationCache</span>). html/WebKitDOMDOMWindow.html:54: warning: no link for: 'WebKitDOMNavigator' -> (<span class="type">WebKitDOMNavigator</span>). html/WebKitDOMDOMWindow.html:94: warning: no link for: 'WebKitDOMHistory' -> (<span class="type">WebKitDOMHistory</span>). html/WebKitDOMDOMWindow.html:115: warning: no link for: 'WebKitDOMStorage' -> (<span class="type">WebKitDOMStorage</span>). html/WebKitDOMDOMWindow.html:121: warning: no link for: 'WebKitDOMBarProp' -> (<span class="type">WebKitDOMBarProp</span>). html/WebKitDOMDOMWindow.html:187: warning: no link for: 'WebKitDOMPerformance' -> (<span class="type">WebKitDOMPerformance</span>). html/WebKitDOMDOMWindow.html:199: warning: no link for: 'WebKitDOMScreen' -> (<span class="type">WebKitDOMScreen</span>). html/WebKitDOMDOMWindow.html:253: warning: no link for: 'WebKitDOMSpeechSynthesis' -> (<span class="type">WebKitDOMSpeechSynthesis</span>). html/WebKitDOMDOMWindow.html:271: warning: no link for: 'WebKitDOMStyleMedia' -> (<span class="type">WebKitDOMStyleMedia</span>). html/WebKitDOMNode.html:764: warning: no link for: 'api-index-2.14' -> (2.14). html/WebKitDOMHTMLTextAreaElement.html:380: warning: no link for: 'WebKitDOMValidityState' -> (<span class="type">WebKitDOMValidityState</span>). html/WebKitDOMHTMLAnchorElement.html:435: warning: no link for: 'WebKitDOMDOMTokenList' -> (<span class="type">WebKitDOMDOMTokenList</span>). html/WebKitDOMElement.html:1021: warning: no link for: 'api-index-2.12' -> (2.12). html/WebKitDOMElement.html:2258: warning: no link for: 'api-index-2.8' -> (2.8). html/WebKitDOMElement.html:2491: warning: no link for: 'api-index-2.10' -> (2.10). html/webkitdomgtk-4.0-WebKitDOMHTMLBaseFontElement.html:102: warning: no link for: 'WebKitDOMHTMLBaseFontElement' -> (<span class="type">WebKitDOMHTMLBaseFontElement</span>). Generating webkit2gtk-4.0 documentation... Copying template files to output directory... Copying HTML files to output directory... Running gtkdoc-scan Running gtkdoc-scangobj Running gtkdoc-mkdb Running gtkdoc-mkhtml Running gtkdoc-fixxref html/WebKitWebInspector.html:248: warning: no link for: 'WebKitWebViewBase' -> (<span class="type">WebKitWebViewBase</span>). html/WebKitSettings.html:4074: warning: no link for: 'api-index-2.14' -> (2.14). html/WebKitSettings.html:4435: warning: no link for: 'api-index-2.3' -> (2.3). html/WebKitWebExtension.html:112: warning: no link for: 'webkit-web-extension-initialize-with-user-data' -> (<code class="function">webkit_web_extension_initialize_with_user_data()</code>). html/WebKitURIResponse.html:195: warning: no link for: 'SoupKnownStatusCode' -> (<span class="type">SoupKnownStatusCode</span>). [100%] Built target gtkdoc [100%] Built target WebKitPluginProcess2 make: *** [Makefile:150: all] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Come on 'make'? Are you kidding? @Michael: Can you tell me, what is probably missing?
I turn GTKDOC=OFF, shouldn't needed for a trace.
Created attachment 344983 [details] trace from coredump/gdb
Created attachment 344984 [details] stacktrace from journalctl
GOOD NEWS: I' managed to compile WebKit2Gtk and MESA, the problem wasn't GKTDOC but just the required diskspace for building (>= 19 GB) WebKit2Gtk. BAD NEWS: The crash currently doesn't happen every time I open a new tab :( But on some websites periodically (some seconds after loading) or after opening special part of the website. Seem to depend on some runtime circumstances. I can provoate a nice crash with this smilie-selector[1]. What seems to be the common point is this:
+ Trace 237107
I really don't know, if this helps, but hope so. [1] http://forum.mods.de/bb/misc.php?view=smilies&window=1
PS: I cannot change Status to "NEW", just "RESOLVED".
Good news! This is https://bugs.webkit.org/show_bug.cgi?id=167296 which is already fixed in WebKit. Look for 2.14.4 hopefully later week.