Bug 163007
| Summary: | [GTK] WebKitWebProces: WebKitDOMNode* webkit_dom_node_append_child(WebKitDOMNode*, WebKitDOMNode*, GError**): assertion 'WEBKIT_DOM_IS_NODE(self)' failed | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andres Gomez Garcia <agomez> |
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | bugs-noreply, mcatanzaro |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| See Also: | https://bugzilla.gnome.org/show_bug.cgi?id=772515 | ||
Andres Gomez Garcia
From quite a long time I've been seeing this messages spit to the log from the WebKitWebProcess:
...
WebKitDOMNode* webkit_dom_node_append_child(WebKitDOMNode*, WebKitDOMNode*, GError**): assertion 'WEBKIT_DOM_IS_NODE(self)' failed
[repeats several times]
...
Specially, when restoring a closed session from Ephy.
I didn't report this before because of the particularities of my running Ephy, but I can still observ this with the distribution packages in current Debian Testing:
WebKit 2.12.5, Ephy 3.20.3
The only difference from a standard installation is that I have set the dconf key:
"process-model" = "shared-secondary-process"
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Michael Catanzaro
This is an Epiphany bug. It would be useful to get a backtrace with G_DEBUG=fatal-criticals. But I think I got one before, looked into it, and couldn't find the problem anyway. :(
Andres Gomez Garcia
(In reply to comment #1)
> This is an Epiphany bug. It would be useful to get a backtrace with
> G_DEBUG=fatal-criticals. But I think I got one before, looked into it, and
> couldn't find the problem anyway. :(
Sorry Michael, but you are not bringing any proof that support your statement. If you link to the proper Ephy bug, feel free to close again.
Michael Catanzaro
I looked for the Ephy bug (pretty sure it exists) but couldn't find it. Anyway, proof is that an application without a web extension will not be using the DOM API at all, that function would never be called. I investigated it before, the error is somewhere in ephy-web-extension.c, I just don't remember where (hence why it would be useful to get another backtrace).
Andres Gomez Garcia
(In reply to comment #3)
> I looked for the Ephy bug (pretty sure it exists) but couldn't find it.
> Anyway, proof is that an application without a web extension will not be
> using the DOM API at all, that function would never be called. I
> investigated it before, the error is somewhere in ephy-web-extension.c, I
> just don't remember where (hence why it would be useful to get another
> backtrace).
I still don't get with that explanation why it should be an Ephy bug. Anyway, won't fight about this. Reported and added into "See Also":
https://bugzilla.gnome.org/show_bug.cgi?id=772515