[Webkit-unassigned] [Bug 121294] New: [GTK] socket_embed_hook hitting not NULL assertion running TestWebKit2
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Sep 13 05:08:36 PDT 2013
https://bugs.webkit.org/show_bug.cgi?id=121294
Summary: [GTK] socket_embed_hook hitting not NULL assertion
running TestWebKit2
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Keywords: Gtk
Severity: Normal
Priority: P2
Component: Tools / Tests
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: mario at webkit.org
CC: gns at gnome.org, apinheiro at igalia.com,
mrobinson at webkit.org, cgarcia at igalia.com
Many CRITICAL errors like the following can be seen now in the GTK bots when running the TestWebKitAPI/TestWebKit2 test suite (see [1]):
[...]
[==========] Running 51 tests from 3 test cases.
[----------] Global test environment set-up.
[----------] 38 tests from WebKit2
[ RUN ] WebKit2.AboutBlankLoad
** (TestWebKit2:29498): CRITICAL **: socket_embed_hook: assertion `spi_global_register != NULL' failed
[ OK ] WebKit2.AboutBlankLoad (171 ms)
[ RUN ] WebKit2.CloseThenTerminate
** (TestWebKit2:29498): CRITICAL **: socket_embed_hook: assertion `spi_global_register != NULL' failed
[ OK ] WebKit2.CloseThenTerminate (172 ms)
[ RUN ] WebKit2.CookieManager
** (TestWebKit2:29498): CRITICAL **: socket_embed_hook: assertion `spi_global_register != NULL' failed
[ OK ] WebKit2.CookieManager (154 ms)
[ RUN ] WebKit2.DidNotHandleKeyDown
[...]
The problem seems to be that the ATK bridge is being properly initialized for the first time that gtk_main() is being called (i.e. for the first test), but then shutdown after that point and never initialized again. Thus, this seems to be a GTK+ bug to me, but still we need to find a way to deal with it here in WebKit IMHO.
[1] http://build.webkit.org/builders/GTK%20Linux%2064-bit%20Release/builds/40662/steps/API%20tests/logs/stdio
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list