useTransition memory overhead in deep component trees

Concurrent Rendering Resource Consumption

The useTransition hook enables React to mark state updates as non-urgent, allowing the engine to interrupt rendering when higher-priority events occur. This mechanism relies on preparing multiple versions of the UI in memory before committing changes to the DOM.

Scaling Constraints

In applications with deeply nested component trees or high-frequency state transitions, the concurrent rendering phase may increase memory pressure. Because React maintains a temporary representation of the UI during the transition, there is a potential for significant overhead when managing large datasets or complex layouts.

What are the specific memory limits or thresholds that trigger the disposal of interrupted render trees? How does React manage the garbage collection of these intermediate UI versions to prevent memory exhaustion in large-scale applications?