-
Notifications
You must be signed in to change notification settings - Fork 27k
fix(router): Fix memory leak through Navigation.abort and canDeactiva… #64141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
a5b0e71 to
dc10b6b
Compare
|
(The change doens't merge cleanly into the patch branch, we'll need a separate PR) |
|
Looks like there are consistent failures |
dc10b6b to
3e63b64
Compare
Fixed. |
…te guards This commit updates the internal transition to handle context retention through the abort function. This retention chain included the previousNavigation and setting this to a noop function resolves the issue. fixes angular#63983
3e63b64 to
d6696f2
Compare
|
This PR was merged into the repository. The changes were merged into the following branches:
|
…te guards (angular#64141) This commit updates the internal transition to handle context retention through the abort function. This retention chain included the previousNavigation and setting this to a noop function resolves the issue. fixes angular#63983 PR Close angular#64141
|
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. |
…te guards
This commit updates the internal transition to handle context retention through the abort function. This retention chain included the previousNavigation and setting this to a noop function resolves the issue.
fixes #63983