Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: d84afd125019bd63f20d7fb42e95fe0fec7de2a5
https://github.com/WebKit/WebKit/commit/d84afd125019bd63f20d7fb42e95fe0fec7de2a5
Author: Ben Nham <[email protected]>
Date: 2026-06-18 (Thu, 18 Jun 2026)
Changed paths:
M Source/WebCore/dom/MutationCallback.h
M Source/WebCore/dom/MutationObserver.cpp
M Source/WebCore/dom/MutationObserver.h
Log Message:
-----------
Distinguish between mutation observer callbacks in normal vs. non-normal
worlds
https://bugs.webkit.org/show_bug.cgi?id=317431
rdar://179843353
Reviewed by Chris Dumez.
We have been getting WebContent hang traces where it seems like the page is
spending an excessive
amount of time hanging the main thread in mutation observer callbacks. However,
we can't tell if
those callbacks are associated with mutation observers installed by the page
vs. mutation observers
installed by injected scripts. Add some non-inlined call frames to the mutation
observer firing
chain to help make our native backtraces in the hang traces more useful.
* Source/WebCore/dom/MutationCallback.h:
* Source/WebCore/dom/MutationObserver.cpp:
(WebCore::MutationObserver::MutationObserver):
(WebCore::MutationObserver::deliver):
(WebCore::MutationCallback::invokeInNonNormalWorld):
(WebCore::MutationCallback::invokeInAutoFillWorld):
* Source/WebCore/dom/MutationObserver.h:
Canonical link: https://commits.webkit.org/315512@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
