Your app runs fine for ten minutes. Then the scroll gets sticky. After half an hour the tab hits a gigabyte. Eventually the page dies with an out-of-memory error and you have no stack trace to show for it.
This is not a render performance problem. The React DevTools Profiler will look quiet because the issue is not how often components redraw. The issue is what stays alive after they unmount. A stray reference somewhere in the JavaScript heap pins an entire tree of DOM nodes, closures, and state. The browser cannot reclaim any of it, so memory climbs until the process collapses.
Reading your source code will not reveal the leak. The bug lives in the gap between what you think unmounted and what the garbage collector actually sees. V8 only frees objects that have zero retaining paths. If a rogue event listener, an uncleared observer, or a long-lived closure holds even one pointer to a fiber or a DOM node, the whole component subtree survives. You unmount a modal, but its detached nodes remain in memory because a listener on window still points to a handler defined inside that modal.
To prove where the leak lives you need to look at the heap, not the editor.
Why the Heap Tells the Truth
Chrome DevTools gives you a direct window into what the garbage collector sees. The Memory tab can record heap snapshots: complete inventories of every object, DOM node, and closure currently held in JavaScript memory. By comparing two snapshots—one before a suspected leak and one after—you can isolate exactly which objects failed to die.
This is not abstract theory. A single leaked React component can retain thousands of detached HTMLElement objects. Those objects are no longer attached to the visible document, but JavaScript references prevent them from being collected. They show up in the comparison view with the constructor name Detached HTMLElement. When you see them multiplying, you have found your leak.
The Chrome DevTools Workflow
Start clean. Close unrelated browser tabs, disable unrelated extensions, and let your application settle into a steady state. Open Chrome DevTools, switch to the Memory tab, and select Heap snapshot. Click Take snapshot. This baseline captures your starting memory footprint.
Now perform the exact user action you suspect. Open and close that heavy modal. Mount and unmount the widget. Navigate to the route and back. Once the UI has returned to its original visual state, click the trash can icon in the Memory tab. This forces a global garbage collection pass. Temporary objects from the render cycle should drop away. Anything that remains is a real candidate for a leak.
Click Take snapshot again. You now have two photographs of memory. Change the view from Summary to Comparison. Set the comparison scope to the first snapshot. The tool will show you only what changed between the two captures, stripping away the noise of the runtime.
Sort by Delta. Look for object counts that grew. Pay special attention to constructors like Detached HTMLElement, Array, Function, or even named class instances from your own codebase. A rising delta means objects were created during your action and were not collected afterward.
Tracing the Retaining Path
When you spot a leaked element, select it. The bottom panel displays the retaining path: a chain of references that explains why this object is still alive. The chain might run from a detached div up through React internal properties, into a closure, and finally land on an event listener registered inside one of your components. That final link in the chain is your line number.
This is where you move from diagnosis to root cause. If the retaining path ends at window.addEventListener, you know a global listener is holding your component hostage. If it ends at an IntersectionObserver instance, you know an observer is still watching a node that should have been garbage collected.
Common Culprits in React
Memory leaks in React usually fall into three patterns.
Orphaned global listeners. A useEffect hooks into window or document to track scroll position, key presses, or resize events. If the effect does not return a cleanup function that calls removeEventListener, the listener survives for the lifetime of the page. Because the listener is a closure, it keeps the entire component scope alive long after React has unmounted the component.
Uncleared observers. IntersectionObserver and ResizeObserver are powerful, but they create native references outside React’s control. If you instantiate an observer inside a component and forget to call disconnect() in the cleanup phase, the observer holds the target DOM node, and the DOM node holds React fibers, props, and state.
Closure traps. When you define a function inside a component and pass it to a third-party library, a global cache, or even setTimeout, that function closes over every variable in its lexical scope. If the external owner keeps the function around, it keeps your whole component scope around with it.
Cleanup Patterns That Actually Work
Fixing a leak means severing every retaining path you found in the snapshot.
Always return a cleanup function from useEffect. If you add a listener in the effect, remove it there.
Use useCallback for any handler you attach to the DOM or window. Without it, every render creates a new function reference. If you call addEventListener with one reference and later call removeEventListener with a different one, the removal fails silently. The original listener stays on window forever. useCallback keeps the reference stable so that add and remove match exactly.
Handle observers with the same discipline. Store the observer instance in a ref or local variable inside the effect. In the cleanup function, call observer.disconnect(). Do not assume unmounting the component kills the observer. It does not.
If your component publishes anything to a global namespace or a singleton service, delete those references on unmount. The V8 engine can only reclaim memory when an object is truly unreachable. Leaving a hook on window or an entry in a module-level Map creates an invisible bridge that keeps the heap growing.
The Real Takeaway
Memory leaks do not crash your app immediately. They accumulate one detached node at a time during long user sessions. The fix is not a library upgrade or a compiler flag. It is the habit of proving your cleanup logic with heap snapshots.
Take a baseline, trigger the suspect flow, force garbage collection, and compare. If the delta shows growth, inspect the retaining path, find the listener or observer that should not exist, and cut the reference. Run the test again. When the delta stays flat, you have actually solved it. Your application will stay responsive, and your users will not lose their work to a frozen browser tab.