[BUG] WebKit (Linux): Assertion error in WKPage._onTargetCreated on a cross-site redirect chain
I maintainer di solito rispondono entro 1 giorno
@yury-s ci sta già lavorando.
Dal 6/10/2026.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 72/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- javascript, typescript
- Ambito
- testing-qa
Direzione di ricerca
Start at WKPage._onTargetCreated and inspect the page-goto.spec.ts regression test named “should work with cross-process redirect chain through visited sites.” Reproduce the Linux WebKit redirect chain with repro.mjs, then verify the assertion is avoided and navigation reaches /done while the regression test passes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Version
1.63.0 (WebKit r2359); also current main (WebKit r2369). 1.64.0-alpha-2026-10-02 is affected as well.
Environment
- Linux:
mcr.microsoft.com/playwright:v1.63.0-noble, GitHububuntu-24.04runners. Headless, and headed underxvfb-run. - macOS (WebKit r2369): not affected.
Steps to reproduce
Three loopback hosts act as three sites: localhost (C), 127.0.0.1 (B), [::1] (A).
The page visits C → B → A by clicking links. A form on A then posts to /go, which returns a 302 to B/hop, which returns a 302 to C/done.
// repro.mjs: node repro.mjs (env: VARIANT=get, PRE=c,b (default), N=3, HEADED=1)
import http from 'node:http';
import { webkit } from 'playwright';
const PORT = 8123;
const H = { a: '[::1]', b: '127.0.0.1', c: 'localhost' };
const method = process.env.VARIANT === 'get' ? 'get' : 'post';
const pre = (process.env.PRE ?? 'c,b').split(',').filter(Boolean);
const server = http.createServer((req, res) => {
const u = new URL(req.url, `http://${req.headers.host}`);
const next = u.searchParams.get('next');
if (u.pathname === '/page') {
res.writeHead(200, { 'content-type': 'text/html' });
const href = next ? `http://${H[next.split(',')[0]]}:${PORT}/page?next=${next.split(',').slice(1).join(',')}` : '/form';
res.end(next ? `<a href="${href}">next</a>` : `<form method="${method}" action="/go"><button>go</button></form>`);
} else if (u.pathname === '/go') {
req.resume(); res.writeHead(302, { location: `http://${H.b}:${PORT}/hop` }); res.end();
} else if (u.pathname === '/hop') {
res.writeHead(302, { location: `http://${H.c}:${PORT}/done` }); res.end();
} else {
res.writeHead(200, { 'content-type': 'text/html' }); res.end('<h1>done</h1>');
}
});
await new Promise(r => server.listen(PORT, '::', r));
const browser = await webkit.launch({ headless: !process.env.HEADED });
let fails = 0;
const N = Number(process.env.N || 3);
for (let i = 0; i < N; i++) {
const page = await browser.newPage();
try {
const hosts = [...pre, 'a'];
await page.goto(`http://${H[hosts[0]]}:${PORT}/page?next=${hosts.slice(1).join(',')}`);
for (let k = 1; k < hosts.length; k++) {
await page.getByRole('link', { name: 'next' }).click();
await page.waitForURL(url => url.host.startsWith(H[hosts[k]]));
}
await page.getByRole('button', { name: 'go' }).click();
await page.waitForURL(/\/done$/, { timeout: 10_000 });
console.log(`run ${i}: ok ${page.url()}`);
} catch (e) {
fails++; console.log(`run ${i}: FAIL ${String(e.message).split('\n')[0]}`);
}
await page.close().catch(() => {});
}
console.log(`variant=${method} pre=${pre.join('>')}>a fails=${fails}/${N}`);
await browser.close(); server.close();
docker run --rm --ipc=host -v "$PWD":/w -w /w mcr.microsoft.com/playwright:v1.63.0-noble \
bash -c 'npm i --silent [email protected] >/dev/null && node repro.mjs'
Expected behavior
The page lands on http://localhost:8123/done, as it does on macOS.
Actual behavior
On the first run, the driver process crashes with an unhandled assertion:
Error: Assertion error
at assert (playwright-core/lib/coreBundle.js:838)
at _WKPage._onTargetCreated (playwright-core/lib/coreBundle.js:47026)
at WKSession.emit ...
In the test runner, the assertion is swallowed and the navigation times out instead.
It reproduces with POST and with GET. It does not reproduce when only one of B and C was visited before, or neither (PRE=b, PRE=).
Analysis
Protocol sequence on Linux:
Target.targetCreated page-25 {isProvisional:true} // swap #1, after the 302 from A to B
[page-25] requestWillBeSent http://127.0.0.1/hop
[page-25] Page.willCheckNavigationPolicy
Target.targetCreated page-28 {isProvisional:true} // swap #2 while page-25 is still provisional -> assert(!this._provisionalPage)
Target.targetDestroyed page-25 // old provisional target is destroyed only after the new one is created
On macOS, provisional page-30 follows the /hop → /done redirect itself and commits, so there is no second swap.
On Linux, WebKit swaps processes again for the redirect target before the first provisional page commits, and it creates the new target before it destroys the old one.
WKPage._onTargetCreated asserts that no provisional page exists yet.
This is a different cause from #37766 (a WebKit SIGABRT on reload) and #42957 (COOP). No COOP/COEP headers are involved.
Proposed fix
In WKPage._onTargetCreated, when a provisional target arrives while _provisionalPage is set, dispose the stale provisional page instead of asserting.
The targetDestroyed that follows for the old id then matches nothing and is a no-op.
A PR with this fix and a regression test (page-goto.spec.ts › should work with cross-process redirect chain through visited sites) follows.
- Lingua principale
- TypeScript
- Stelle
- 100k
- Fork
- 6.9k
- Merge medio
- 16h 8m
- PR unite (30g)
- 281
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoft/playwright
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
microsoft/playwright#44289 ·
I maintainer di solito rispondono entro 1 giorno
-
agent-triage-done
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
microsoft/playwright#44264 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
[BUG] WebKit keeps every removed iframe's JS heap alive (memory grows until the page crashes)Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
microsoft/playwright#44290 ·
I maintainer di solito rispondono entro 1 giorno
-
[Regression]: requestFullscreen() in a popup rejects with "not granted" in 1.65 (Chromium 159)Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
microsoft/playwright#44288 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug]: page.goto never returns for a load started as a newer service worker takes over (Chromium)Aperta
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
microsoft/playwright#44287 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di microsoft/playwright
Issue simili
-
clawsweeper:needs-maintainer-review clawsweeper:needs-product-decision clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
openclaw/openclaw#203385 · 1 commento · 1 reazione ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
nwverse/persona#12800 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
I maintainer di solito rispondono entro 1 giorno
-
good first issue
Difficoltà 2/5 Mezza giornata Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
WISE-Community/WISE-Client#2404 ·
I maintainer di solito rispondono entro 1 giorno