fix: memory leak in MainThreadWorkspace #283450
Open
+12
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a memory leak in MainThreadWorkspace.
Details
When a provider is registered, it is both added to a Map called
registeredEditSessionProvidersas well as tothis._toDispose.However when a provider is unregistered, it is removed from the Map
registeredEditSessionProviders, but not fromthis._toDisposeThis causes the
this._toDisposearray to grow over time.Change
The change is using a
DisposableMap, ensuringthis._toDisposedoesn't grow when registering and unregistering providers.Before
When restarting extensions 37 times, the number functions in
MainThreadWorkspace.$registerCanonicalUriProviderseems to grow by 3 each time. Entries 10/11:After
When restarting extensions 37 times, the number functions in
MainThreadWorkspace.$registerCanonicalUriProviderstays constant: