memory-leak-audit

Replace raw addEventListener or property handlers like .onclick with addDisposableListener, and register the result via this._register so it is disposed with the class. For one-time events, wrap the event with Event.once so the listener auto-removes after firing.

MutableDisposable holds at most one disposable, replacing the previous value on each assignment, which suits methods called repeatedly. DisposableStore collects many disposables and releases them all at once, which suits model-tied or item-scoped lifetimes.

Each call to this._register inside a non-constructor method adds another listener to the class store, so registrations grow linearly with invocations. Use a MutableDisposable field or return an IDisposable to the caller instead.

Call ensureNoDisposablesAreLeakedInTestSuite at the top of the test suite so leaked disposables fail the tests automatically. Also compare listener counts before and after repeated operations to confirm counts stabilize.

Use Event.once for lifecycle events that should fire only once, such as disposal, close, or first-change notifications. A regular subscription stays registered after the first fire, leaking the listener for the emitter's lifetime.