114 wires and counting
$ status: archived — this briefing has stopped; the archive stays readable. browse live briefings →

$ status

wire 2026-08-23
stories 5

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

React plugs memory leaks in Flight and Fizz

By RepoJournal · Filed · About Meta · Composed from the cited sources · methodology

React's server rendering stack just got a memory fix that matters for long-lived signals.

React's server renderer was leaking entire rendered outputs in memory for as long as a caller's AbortSignal lived. Two patches from unstubbable fix this: one stops the caller's signal from retaining a finished render [1], the other aborts the cache signal when debug objects are retained [2]. For Flight, debug objects that exceed the model's object limit stay retained until the client asks for them, which kept renders alive longer than needed. Composite signals from AbortSignal.any() and timeout signals are the worst offenders, because the runtime holds onto them for the lifetime of the process. These fixes close that leak on the success path, where the abort listener previously stayed attached. Over in React Native, a routine Flow upgrade in fbsource [3] landed, nothing to rush for. This is the kind of cleanup you want in before your next server render spike.

Quick answers

What shipped in Meta on August 23, 2026?
React's server rendering stack just got a memory fix that matters for long-lived signals. In total, 3 commits and 2 pull requests landed.
Who contributed to Meta on August 23, 2026?
1 developer shipped this update, including unstubbable.
What were the notable Meta updates?
[Flight/Fizz] Stop the caller's signal from retaining a finished render, [Flight] Abort the cache signal when debug objects are retained, and Upgrade Flow in fbsource (#58076).