memory-leak-audit

To find memory leaks in VS Code extension development, review event listeners and disposable cleanup patterns for unmanaged raw assignments. Verifying tracked disposal logic ensures lingering DOM handlers and forgotten disposables are caught before they accumulate and slow down features.

Memory leaks from event listeners and disposables are caused by forgotten cleanup in lifecycle callbacks and unmanaged event subscriptions. When raw assignments bypass tracked disposal patterns, registrations accumulate over repeated method calls and model-scoped stores, ultimately degrading application performance.

To ensure safe disposable cleanup for one-time events, verify that patterns like Event.once and MutableDisposable are properly managed within a DisposableStore. Checking onWillDispose callbacks prevents runaway registrations and guarantees resources are released after execution.

Yes, this memory leak audit works for test suites and pooled objects by verifying the ensureNoDisposablesAreLeakedInTestSuite pattern. It checks that test suites safely create and dispose of objects, catching leaks early with automated checks before code is shipped.

The best way to audit DOM handlers for disposable cleanup issues is to review subscriptions for tracked disposal patterns instead of raw assignments. Using addDisposableListener ensures DOM handlers are properly tied to lifecycle callbacks and unregistered safely.

A VS Code feature slows down after repeated opens and closes due to memory leaks from lingering event listeners and forgotten disposables. Unmanaged listener registrations accumulate in model-scoped stores across lifecycle callbacks, consuming resources and degrading runtime performance.