Next Js Daily: Plugging the Long-Running Server Leaks
A cluster of fixes today target memory growth in long-lived Next.js servers — timeouts, compression streams, and cache keys — alongside a major dev-mode performance push that moves Cache Components validation off the main thread and fixes how source maps get resolved.
Duration: PT2M54S
Episode overview
This episode is a short developer briefing from Next Js Daily.
It explains recent repository work in plain language.
- Show: Next Js Daily
- Published: 2026-07-25T22:00:32Z
- Audio duration: PT2M54S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
You're listening to Next Js Daily. It's July 25th, 2026.
The clearest signal today: several separate teams independently found the same class of bug — long-running Next.js servers slowly leaking memory until they get OOM-killed. That's the headline.
Pete Hunt landed two of these. PR 96161 fixes the Edge sandbox's timeout tracker, which held onto one-shot timeout IDs forever, even after they'd fired — causing step-wise heap growth in standalone deployments. PR 96173 is the more dramatic one: when a client disconnects mid-response, the compression middleware's…
Related: Gaearon and Marcos Hernanz followed up with PR 96229 and PR 96231, which fix a subtler leak — byte-budgeted LRU caches that counted the size of cached values but treated the cache keys themselves as free. Long URLs or unique paths could quietly inflate memory beyond the configured budget. This traces back…
The second theme is dev-mode responsiveness. Unstubbable's multi-PR effort — 96151, 96153, 96149, 96148 — moves Cache Components validation onto a worker thread so rapid navigation doesn't stall the event loop. Benchmarks in PR 96152 showed multi-second worst-case stalls in-process, gone entirely once validation…
Tied…
Nearby episodes from Next Js Daily
- Squashing Memory Leaks and Chasing Deopts
- TypeScript 7 Fire Drill and Static Rendering Guardrails
- Dev Cache Gets an Honesty Fix
- Security Patches and Turbopack's Path Problem
- Hardening the Edges of Cache Components and Turbopack
- Chasing Down Dev Server Memory Leaks
- Duplicate Data, Duplicate Fixes
- Navigation Reliability Under the Microscope