fix: memory leak in history service #279246
Merged
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
historyServiceby removing the editor groupwillMoveEditorevent listener when the group is removed.Before
Extra functions/closures are created by
EditorNavigationStack.registerGroupListeners:After
No more extra functions/closures are created by
EditorNavigationStack.registerGroupListeners:Details
In
historyService.ts, awillMoveEditorlistener is added to a group. However when the group becomes closed / disposed, the listener doesn't seem to be removed.Additional Details
In the historyService code there is a actually group remove remove function, which should dispose the move event listener. The code looks correct to me and I'm not sure why it seems to be not working.
An ideal solution would probably be to get the existing remove code to work instead of registering another group remove listener. I tried, but couldn't figure out the exact issue why it's not working. Maybe someone can figure it out :)