How a Stale JavaScript Closure Silently Degraded a Dashboard for 20 Minutes

An operations team's data dashboard worked fine initially but became progressively sluggish after about 20 minutes of continuous use, prompting users to refresh the page out of habit. The culprit was an asynchronous polling loop set up at component mount that closed over the initial state and was never cleaned up or resynchronized. Because JavaScript closures capture an entire lexical environment — not just the variables explicitly referenced — the original state object remained pinned in memory throughout the session. Engineers initially suspected framework rendering issues, but the true cause was a fundamental closure behaviour where the garbage collector cannot free any part of a retained scope. The incident highlights how closures, while powerful for encapsulation and private state, become a source of stale data bugs and quiet memory bloat in reactive, event-driven architectures where callbacks outlive the code that created them.