Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 57438b0e69831fedd7851825b33b09a0917c9b74
https://github.com/WebKit/WebKit/commit/57438b0e69831fedd7851825b33b09a0917c9b74
Author: Lauro Moura <[email protected]>
Date: 2026-03-12 (Thu, 12 Mar 2026)
Changed paths:
M Source/WebCore/accessibility/atspi/AccessibilityAtspi.cpp
M Source/WebCore/accessibility/atspi/AccessibilityAtspi.h
M Source/WebKit/WebProcess/glib/WebProcessGLib.cpp
Log Message:
-----------
[GLIB] WebProcess critical assertion during D-Bus RequestName completion on
process shutdown
https://bugs.webkit.org/show_bug.cgi?id=309693
Reviewed by Claudio Saavedra.
While rare, there's a chance that the WebProcess exits while the
AccessibilityAtspi dbus name callbacks are still in flight. If we don't
close them gracefully, we risk critical errors when the reply arrives.
This is likely related to 284894@main, which added the support for
well-known bus name to AccessibilityAtspi.
This happens, for example, in some WebDriver tests that quickly open and
close browsing contexts. A run with release asserts is reporting almost
30 crashes.
This commit addresses this issue by adding a graceful cleanup path to
AccessibilityAtspi.
* Source/WebCore/accessibility/atspi/AccessibilityAtspi.cpp:
(WebCore::AccessibilityAtspi::didConnect):
(WebCore::AccessibilityAtspi::disconnect):
* Source/WebCore/accessibility/atspi/AccessibilityAtspi.h:
* Source/WebKit/WebProcess/glib/WebProcessGLib.cpp:
(WebKit::WebProcess::stopRunLoop):
Canonical link: https://commits.webkit.org/309174@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
