Bug 153649 - [GTK] WebProcess from WebKitGtk+ 2.10.x spits a lot of criticals in webkit_dom_node_append_child
Summary: [GTK] WebProcess from WebKitGtk+ 2.10.x spits a lot of criticals in webkit_do...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Local Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-29 05:57 PST by Andres Gomez Garcia
Modified: 2017-01-31 08:05 PST (History)
5 users (show)

See Also:


Attachments
BT from gdb, when running epiphany with the env variable G_DEBUG=fatal_criticals (23.94 KB, text/plain)
2016-02-10 02:36 PST, Andres Gomez Garcia
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Gomez Garcia 2016-01-29 05:57:18 PST
I'm using WebKitGtk+ with my own JHBuild setting:
https://github.com/tanty/jhbuild-epiphany/tree/master

Epiphany 3.18.0 and WebKit 2.10.6

I'm running Epiphany with the dconf key:

"process-model" = "shared-secondary-process"

The compilation was done with CMake args:

'-DPORT=GTK -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS" -DCMAKE_CXX_FLAGS_RELEASE="-O0 -g1 -DNDEBUG -DG_DISABLE_CAST_CHECKS"'

---

I launch Epiphany from the command line. When browsing, I see every now and then a lot of this messages in a row in my terminal:

** (WebKitWebProcess:10658): CRITICAL **: WebKitDOMNode* webkit_dom_node_append_child(WebKitDOMNode*, WebKitDOMNode*, GError**): assertion 'WEBKIT_DOM_IS_NODE(self)' failed

I've been seeing this for quite a while now, maybe even also in the 2.8.x series.
Comment 1 Michael Catanzaro 2016-01-29 07:21:47 PST
Decent chance this is an Epiphany bug. Only way to find out is to get a backtrace. If you run with G_DEBUG=fatal-criticals you'll get a crash next time you hit the critical.
Comment 2 Andres Gomez Garcia 2016-02-10 02:36:07 PST
Created attachment 270983 [details]
BT from gdb, when running epiphany with the env variable G_DEBUG=fatal_criticals

This critical seems, somehow, related with epiphany's "about:overview" tab.

The steps to reproduce are not reliable. Sometimes in a running session I see them all the time and sometimes never.

But, when it is actually happening, a way of forcing it to happen is:
1. Open some "about:overview" tab.
2. From it, open with the secondary mouse button a new tab, from the "favorites" grid.
3. Move from tab clicking in the new opened tab that was loading in the background.
4. Click in the "x" to close that new tab. The focus moves automatically to the previous "about:overview" tab from which the newest closed tab was opened.

In the moment of closing and automatically returning to the previous "about:overview" tab, several CRITICALs appear in the terminal.
Comment 3 Michael Catanzaro 2017-01-31 08:05:42 PST
This is an Epiphany bug, not a WebKit bug. I think I might have fixed it in https://git.gnome.org/browse/epiphany/commit/?h=gnome-3-22&id=55a08b7b29b71e0fa6c0b2092bfdf410455257e2, but I'm not sure. At least I'm not able to reproduce it following your instructions. Can you check to see if it's fixed? If you see it again with 3.22.5, please report it on GNOME Bugzilla. (INVALID because it's not a WebKit bug, although it is a valid Epiphany bug.)