React Daily: Plugging a Fragment Refs Memory Leak
A single fix in React's Fragment Refs system closes a gap where deleted children weren't unregistered from observers, addressing a leak that spanned both DOM and native Fabric implementations.
Duration: PT2M11S
Episode overview
This episode is a short developer briefing from React Daily.
It explains recent repository work in plain language.
- Show: React Daily
- Published: 2026-08-17T06:00:25Z
- Audio duration: PT2M11S
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 August 17th, 2026, and this is React Daily.
Today's codebase activity centers on one fix, but it's a meaningful one: a cleanup bug in how React tracks Fragment children under observation.
Here's the issue. When a Fragment child gets inserted, React registers it with any active Intersection Observer or Resize Observer through a function called "commit new child to fragment instance." But the teardown path — "delete child from fragment instance" — never called the matching "unobserve." That's the kind…
PR 37302, from MHJahanbakhsh, fixes this by mirroring the insert-side observation call on the delete path. Notably, the fix was applied consistently across both React DOM's fiber config and the Fabric fiber config used for native platforms — meaning this wasn't a DOM-only quirk, but a shared pattern in how Fragment…
The takeaway here is less about this specific bug and more about the pattern it reveals: any time a lifecycle feature adds a "register on mount" behavior, the corresponding "unregister on unmount" needs matching test coverage, and it's worth checking both renderer implementations when a feature spans DOM and Fabric.
What's next: watch for this fix landing…
Nearby episodes from React Daily
- Hardening the Render Loop
- Cross-Renderer Parity and a Server Memory Leak Fix
- DevTools Extension Builds Get More Reproducible
- Weekly Recap - Fixing Fragments and Hardening the Render Pipeline
- Cutting Wasted Work in the Fiber Tree
- DevTools Gets a Reliability Sweep
- Fixing Edge Cases in Events, Logging, and Server Memory
- DevTools Consistency Cleanup and Fiber Cleanup Fixes