fix(upgrade): clean up scope when element is destroyed#8102
Closed
andreialecu wants to merge 1 commit intoangular:masterfrom
Closed
fix(upgrade): clean up scope when element is destroyed#8102andreialecu wants to merge 1 commit intoangular:masterfrom
andreialecu wants to merge 1 commit intoangular:masterfrom
Conversation
mhevery
added
pr_state: LGTM
action: merge
|
Merging PR #8102 on behalf of @robertmesserle to branch presubmit-robertmesserle-pr-8102. |
|
Merging PR #8102 on behalf of @robertmesserle to branch presubmit-robertmesserle-pr-8102. |
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
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 bug with change detection still being processed for destroyed components, and is a memory leak fix in itself.
I'm not sure how to test it since the error that this fixes is not catchable. It happens in a change detector.
See #8100
The only change is to properly dispose the cloned scope when the element is destroyed.
No