[BUG] WebKit keeps every removed iframe's JS heap alive (memory grows until the page crashes)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 12/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- javascript, nodejs, playwright, typescript
- Ambito
- testing-qa
Direzione di ricerca
The report is a memory leak in Playwright's WebKit build or inspector backend, so it is not a first-timer task. Start from the repro script in the issue body, which removes iframes in a loop and reads WebContent RSS with ps. Done would mean a fix that keeps RSS flat, which needs WebKit-side or protocol-side debugging well beyond a newcomer's scope.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Version
- Playwright 1.65.1, WebKit revision 2388 (Linux WPE build and macOS build)
- Node.js 26.13.1
- OS: Ubuntu 26.04 (GitHub Actions
ubuntu-26.04image, 4 CPU, 16 GB); macOS 27.2 - Found through Vitest 5.1.1 browser mode (
@vitest/browser-playwright5.1.1), which
runs each test file in a new same-origin iframe and removes it after. The repro
below does not use Vitest.
Steps to reproduce
Save as repro.mjs and run node repro.mjs:
import { execSync } from "node:child_process";
import { webkit } from "playwright";
const CHILD =
"<script>window.big = Array.from({ length: 300000 }, (_, i) => ({ i, s: 'x' + i }));</script>";
const rss = () =>
execSync("ps -eo rss=,comm=")
.toString()
.split("\n")
.filter((l) => /WPEWebProcess|WebContent/.test(l))
.map((l) => Math.round(Number(l.trim().split(/\s+/)[0]) / 1024))
.join(" ");
const browser = await webkit.launch();
const page = await browser.newPage();
await page.route("http://leak.test/**", (route) =>
route.fulfill({
contentType: "text/html",
body: route.request().url().endsWith("/child") ? CHILD : "<body></body>",
}),
);
await page.goto("http://leak.test/");
for (let i = 0; i <= 200; i++) {
await page.evaluate(async () => {
const frame = document.createElement("iframe");
frame.src = "/child";
const loaded = new Promise((r) => (frame.onload = r));
document.body.append(frame);
await loaded;
await new Promise((r) => setTimeout(r, 50));
frame.remove();
});
if (i % 25 === 0) console.log(i, "iframes, WebContent RSS MB:", rss());
}
await browser.close();
Expected behavior
The memory of a removed iframe is reclaimed. RSS stays flat.
Actual behavior
RSS grows by about 36 MB per removed iframe (the size of the child's window.big)
and is never reclaimed. It grows linearly and does not level off:
| Removed iframes | Linux WPE (CI) | macOS Playwright WebKit | Chromium (same script) |
|---|---|---|---|
| 0 | 273 MB | 149 MB | 107 MB |
| 100 | 3,883 MB | 3,756 MB | - |
| 200 | 7,460 MB | 7,333 MB | 264 MB |
On Linux, the content process crashes at about 8.5 GB ("page crashed").
Findings:
- Reachability decides it. A child that allocates the same data in a block-scoped
const(garbage at load) does not leak: 147 MB → 403 MB after 200 iframes. So
the removed iframe's global object stays reachable. - None of these change the result (identical numbers): an open or closed
BroadcastChannelin the child, a listener onparent, an openWebSocket, and
navigating the iframe toabout:blankbefore removal. - Playwright's automation is not the trigger. A page that adds and removes the
iframes by itself, with nopage.evaluateorpage.route, leaks the same in
Playwright WebKit: 4.8 GB after 129 iframes. - System WebKit does not leak. The same self-driving page in a system
WKWebView
(macOS 27.2) stays flat at about 264 MB for 200 iframes. That points at Playwright's
WebKit build or its inspector backend, not at WebKit itself.
Impact
Vitest browser mode on WebKit grows each page by the full heap of every finished test
file. A 185-file suite reaches about 8 GB per page and crashes the page (or exhausts a
16 GB CI runner with three pages).
- 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
-
[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
-
[MCP] browser_tabs list/select indices diverge across HTTP sessions with --shared-browser-contextAperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
microsoft/playwright#44279 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di microsoft/playwright
Issue simili
-
good first issue
Difficoltà 2/5 Mezza giornata Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
blamechris/chroxy#9272 ·
I maintainer di solito rispondono entro 1 giorno
-
no-repo-link tool-submission
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 66/100
BraveOPotato/NoSignups#2458 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
drmrd/vernacular#1061 ·
I maintainer di solito rispondono entro 1 giorno
-
[Bug] PUT /profiles/{id} silently drops design_prompt — designed voice profiles cannot be editedAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100