Branch: refs/heads/main
Home: https://github.com/WebKit/WebKit
Commit: e7dc9797f7ed88f66a2ebb94f8d920968a9d2c05
https://github.com/WebKit/WebKit/commit/e7dc9797f7ed88f66a2ebb94f8d920968a9d2c05
Author: Adrian Taylor <[email protected]>
Date: 2026-08-03 (Mon, 03 Aug 2026)
Changed paths:
M Tools/TestWebKitAPI/Runner/GoogleTestsController.swift
Log Message:
-----------
Fix threadsafe deathtest explosion
https://bugs.webkit.org/show_bug.cgi?id=319490
rdar://182221871
Reviewed by Geoffrey Garen.
Some of our tests are "death tests" which rely on spawning a new process to
ensure that it crashes as expected. Some of them, in turn, are "threadsafe"
which means that the test runner launches an entire new test executable
(instead of just using 'fork()').
These tests have recently become broken because of a problem passing through
arguments to those new child processes. This resulted in an infinite cascade of
new TestWTF processes, each immediately spawning another, until we got resource
exhaustion on the Mac, which removed it from the EWS pool.
This adds support for the required command-line arguments.
To reproduce this problem,
Tools/Scripts/run-api-tests --debug
TestWTF.WTF_RunLoopDeathTest.CapabilityIsCurrentFailureAssertsDeathTest
while running something like
watch 'ps ax | grep -c "[T]estWTF"'
and be ready to killall -9 TestWTF before your Mac is taken down.
Before this fix, you will see hundreds of processes being spawned within
moments.
Canonical link: https://commits.webkit.org/318480@main
To unsubscribe from these emails, change your notification settings at
https://github.com/WebKit/WebKit/settings/notifications
