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.
This fixes a memory leak related to context keys. In
contextkeys.tsthere is this function:When a new window is registered, for each window it adds a
focusinevent listener for updating the context keys.The memory leak problem seems to be that it passes the
disposablesof this window to theupdateInputContextKeysfunction.Here the
FocusTrackerdisposable is added todisposableseach time an input element in the window is being focused, makingdisposablesgrow each time.For example:
disposablesarray of this windowFocusTrackeris being added to thedisposablesarrayFix
The fix uses a
MutableDisposableto dispose and overwrite the previous focus trackers.This way when an input element in the window is focused, the previous
FocusTrackerwill be unreferenced by settingmutableDisposable.valuewith the newDisposableStore.Before
When showing and hiding the quickpick 31 times, the number of
FocusTrackerinstances increases each time from 63 to 125:After
When showing and hiding the quickpick 31 times, the number of
FocusTrackerstays constant at 63: