Fix for issue #6265 - memory leak in uppy angular components#6374
Open
costescuandrei wants to merge 1 commit into
Open
Fix for issue #6265 - memory leak in uppy angular components#6374costescuandrei wants to merge 1 commit into
costescuandrei wants to merge 1 commit into
Conversation
Memory leak in 3 classes that instantiate Uppy (& document listeners) but fail to destroy it - derived from UppyAngularWrapper. See issue description for more info.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It was a memory leak - the instantiated Uppy was never destroyed, leaking Uppy instances via document listeners that were never removed.
See issue description for more details.