Next Js Daily: Chasing Down Dev Server Memory Leaks
Three separate pull requests target memory blowups and stale output in the development server, with source maps as the common culprit, while a fourth improves how the server responds to non-page requests.
Duration: PT2M33S
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-19T22:00:55Z
- Audio duration: PT2M33S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's July 19th, 2026, and this is Next Js Daily.
Today's biggest signal is memory. Multiple pull requests are independently chasing down out-of-memory crashes in the dev server, and they all point back to how source maps are handled.
Gaearon opened two related fixes. PR 95936 tackles a case where Node.js permanently retains parsed source maps for React's fake stack frames, because each one gets embedded as a data URL. Instead, this change serves those maps by reference, over the same endpoint used in PR 71042. Worth noting: the author flagged…
The second piece is PR 95934, which stops copying full source content into every serialized Turbopack source map. The author's own measurements show peak memory dropping from around 3 gigabytes to 2.6 gigabytes when rapidly navigating routes. Different mechanism, same underlying problem: source maps are expensive,…
A second theme is correctness in dev mode caching and rendering. PR 95939, from Tim Neutkens, fixes instant validation running before a navigation response has actually finished, which could block or interfere with page loads. It also adds cancellation support so stale validation work gets superseded rather than…
Smaller…
Nearby episodes from Next Js Daily
- Duplicate Data, Duplicate Fixes
- Navigation Reliability Under the Microscope
- Chasing Down Tracing and Runtime Regressions
- Async Loading Fixes and Benchmark Overhaul
- Request Insights Comes Together
- Vercel Adapter Hardening and Turbopack Precision Fixes
- Request Insights Land, Turbopack Trims the Fat
- Cache Components Tighten Their Rules on Sync IO