memory-leak-audit

To find memory leaks in a VS Code extension, audit unsafe listener registrations and verify the use of tracked disposable patterns like addDisposableListener and DisposableStore. This identifies lingering DOM handlers that prevent proper resource cleanup.

The correct disposable lifecycle pattern for one-time events involves using Event.once and MutableDisposable. This ensures that subscriptions are automatically cleaned up after a single execution, preventing listener counts from growing over time.

To audit disposable misuse for model-bound resources and pooled objects, review code paths for correct disposal lifecycle patterns. Verify that repeated method calls and pooled objects properly track and dispose of resources to prevent accumulation.

To ensure test suites catch leaked disposables in VS Code development, apply the ensureNoDisposablesAreLeakedInTestSuite pattern. This validates that every test actively checks for leaked resources, catching lifecycle regressions early.

Yes, this memory leak audit works with Electron codebases by identifying unsafe listener registration and disposable lifecycle patterns. It specifically applies to repeated method calls, model-bound resources, and pooled objects to prevent resource accumulation.