Browser: headless Chrome reached 11 GB RSS on stacks-images branch (OOM) #47

Open
opened 2026-09-27 14:57:26 +00:00 by kayg · 0 comments
Owner

At 16:56 IST on 2026-09-27, the kernel OOM-killed the headless Chrome of job verify-24 (branch stacks-images, step 24, #41) while scripts/verify browser ran:

Out of memory: Killed process 1966529 (chrome-headless) total-vm:1532279784kB, anon-rss:11357604kB

That is 11.3 GB anonymous RSS in one browser. The job died partway through its run, just after the Playwright suite passed the inventory route checks. The VM has about 170 containers, most of them test fixtures.

Suspects: the stacks, images or volumes pages (unbounded list rendering, a stack-log subscription loop, or a filter-generation or retry loop that keeps allocating), or the shared log view.

Needed:

  • reproduce it with a memory profile (for example performance.memory or a CDP heap snapshot per route) on this branch against dev;
  • find the route and the cause;
  • fix it;
  • add a browser-gate assertion that each route's JS heap stays under a bound, for example 200 MB.

This blocks step 24's verify.

At 16:56 IST on 2026-09-27, the kernel OOM-killed the headless Chrome of job verify-24 (branch `stacks-images`, step 24, #41) while `scripts/verify browser` ran: ``` Out of memory: Killed process 1966529 (chrome-headless) total-vm:1532279784kB, anon-rss:11357604kB ``` That is **11.3 GB anonymous RSS in one browser**. The job died partway through its run, just after the Playwright suite passed the inventory route checks. The VM has about 170 containers, most of them test fixtures. Suspects: the stacks, images or volumes pages (unbounded list rendering, a stack-log subscription loop, or a filter-generation or retry loop that keeps allocating), or the shared log view. Needed: - reproduce it with a memory profile (for example `performance.memory` or a CDP heap snapshot per route) on this branch against `dev`; - find the route and the cause; - fix it; - add a browser-gate assertion that each route's JS heap stays under a bound, for example 200 MB. This blocks step 24's verify.
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/infraternal-v0#47
No description provided.