A registered listener is reachable from the DOM node, so captured values stay reachable too.
Heap usage grows after repeated navigation, polling, subscriptions, cache writes, or background work. Clean up window, document, and shared element listeners in component lifecycles.
Removing DOM without removing listeners on long-lived targets.
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.
Related cases
Continue with nearby confusion while the mental model is fresh.
Was this clear?
This stays local for now. It helps you track where the product still needs sharper cases.