closure memory hold

Heap usage grows after repeated navigation, polling, subscriptions, cache writes, or background work. Closures are useful for caches and private state, but can accidentally retain large objects.

Assuming local variables always disappear when a function returns.

Remove long-lived references, clear timers/listeners, and verify the object can be collected.

const id = setInterval(tick, 1000);
return () => clearInterval(id);

The visual proof is the active runtime event: watch what is retained, blocked, queued, or released at each step.

Repeat the workflow several times, take a heap snapshot, and confirm retained listeners, timers, or cached objects stop growing after cleanup.