memory-leak-audit

To audit TypeScript code for memory leaks, enforce disposable patterns by checking that event listeners and lifecycle handlers are correctly disposed using structures like DisposableStore and addDisposableListener during code reviews.

Common memory leak patterns in TypeScript UI components include raw event handlers, repeated listener registrations, and non-cleanup lifecycle hooks. These issues are detected by verifying proper cleanup via disposable patterns like MutableDisposable.

Ensure proper disposal of event subscriptions by applying patterns like Event.once and DisposableStore. This verifies that subscriptions added in constructors or repeatedly are correctly cleaned up to prevent memory leaks.

You need disposable patterns in TypeScript applications when reviewing code with long-running services, extensions, or UI components that register listeners. This ensures objects are disposed correctly and prevents performance degradation from memory leaks.

Yes, this memory leak audit applies to TypeScript services, models, and extensions with long lifetimes that register listeners. It provides a structured checklist to verify proper cleanup of event subscriptions and lifecycle handlers.