All Production Symptoms
Production Symptom5 Causal Mechanisms

SPA dashboard climbs to 2.4 GB RAM and crashes with Aw, Snap!

Long-lived event listeners, uncleaned MutationObservers, and stale hook closures retain detached DOM subtrees across route transitions until V8 hits the heap limit.

DevTools / RUM Signature
DevTools Memory Heap Snapshot shows growing Detached HTMLDivElement retainers and uncancelled AbortController/Observer closures

Causal Chain of Browser Mechanisms

Ordered from trigger to root invariant. Open any mechanism to inspect its internals or reproduce the behavior in an interactive lab.

Step 1
JS RuntimeBaseline · Widely

Prevent frame-drop GC pauses by understanding V8's Orinoco collector—short-lived objects evacuate between Young Generation semi-spaces while Old Generation marks concurrently.

Step 2
JS RuntimeBaseline · Widely

Unintended strong reference paths from GC roots—often via global listeners, timers, or shared closure Contexts—that pin dead objects and detached DOM trees.

Step 3
State & ArchitectureBaseline · Widely

Explains how JavaScript lexical closures snapshot primitive state per render, causing timers, listeners, and suppressed dependency arrays to read outdated values.

Step 4
DOM & EventsBaseline · Widely

Replace main-thread-freezing Mutation Events with batched microtask delivery—MutationObserver queues DOM edits silently and flushes MutationRecord[] once after the Call Stack unwinds.

Step 5
JS RuntimeBaseline · Widely

Kill-switch for in-flight fetch calls, DOM listeners, and async tasks you should have stopped three renders ago—without boolean isMounted flags.

Seen in Architecture Autopsies