Bug 309693
| Summary: | [GLIB] WebProcess critical assertion during D-Bus RequestName completion on process shutdown | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Lauro Moura <lmoura> |
| Component: | WebKitGTK | Assignee: | Lauro Moura <lmoura> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | bugs-noreply |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Lauro Moura
This is happening rather frequently during the WebDriver tests with the sandbox enabled, especially on tests that open and close pages quickly. A full test run triggers ~27 crashes, but as they happen after shutdown started, they don't make the test record a failure.
During the WebProcess shutdown, we get the following message:
(WPEWebProcess:1260459): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
Enabling DBUS logging shows:
GDBus-debug:Call:
<<<< ASYNC COMPLETE org.freedesktop.DBus.RequestName()
FAILED: The connection is closed
At first, I thought it was directly related to the sandbox, but it's actually related to the AccessibilityAtspi name request DBus callbacks being called after the WebProcess already started its shutdown process. Likely the sandbox overhead increases the chances of such condition.
Tentative patch incoming.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Lauro Moura
Pull request: https://github.com/WebKit/WebKit/pull/60411
EWS
Committed 309174@main (57438b0e6983): <https://commits.webkit.org/309174@main>
Reviewed commits have been landed. Closing PR #60411 and removing active labels.