Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: 3e664d3ff8b92d41686b0d8174fe384db718565f
https://github.com/WebKit/WebKit/commit/3e664d3ff8b92d41686b0d8174fe384db718565f
Author: Alex Christensen <[email protected]>
Date: 2025-12-16 (Tue, 16 Dec 2025)
Changed paths:
M LayoutTests/fast/dom/connected-subframe-counter-overflow.html
M LayoutTests/platform/ios/TestExpectations
M LayoutTests/platform/mac-wk2/TestExpectations
Log Message:
-----------
REGRESSSION (299195@main): [Debug] fast/dom/document-all.html is a constant
timeout
https://bugs.webkit.org/show_bug.cgi?id=298256
rdar://159688229
Reviewed by Ryosuke Niwa.
Somewhere around 299195@main but almost certainly not caused by 299195@main,
something changed that caused fast/dom/document-all.html to time out. It was
timing out
because a previous test, fast/dom/connected-subframe-counter-overflow.html, was
leaving
1024 ScriptExecutionContexts in the EventLoop's m_associatedContexts, which
caused it
to spend a lot of time iterating them in the MicrotaskCheckpointScope
constructor.
After investigating I found that the only thing keeping them alive was the lack
of GC.
Since connected-subframe-counter-overflow.html is an exceptional test that does
something
very unusual, explicitly tell the garbage collector to clean up afterwards and
then
we don't have this issue.
* LayoutTests/fast/dom/connected-subframe-counter-overflow.html:
* LayoutTests/platform/ios/TestExpectations:
* LayoutTests/platform/mac-wk2/TestExpectations:
Canonical link: https://commits.webkit.org/304528@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
