-
Notifications
You must be signed in to change notification settings - Fork 59
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
[Transition][memory leak] Dispose unused transition #55
Comments
3 tasks
when will this bug be fixed? |
reopened per uirouter/angularjs comment angular-ui/ui-router#3603 |
wawyed
pushed a commit
to wawyed/core
that referenced
this issue
Mar 3, 2018
The treeChanges object has references to the PathNodes from the previous transition (`.treeChanges("from")`). The PathNode object has resolve data inside it. The previous transition is reachable via a resolve (via tokens: `"$transition$"` or `Transition`). Through this chain, all other transitions are reachable and not eligible for GC. This change cleans out the previous Transition object from the resolves, but only after a transition has been evicted from the `successfulTransitions` queue. The `successfulTransitions` queue currently has a max size of 1, so the transition is cleaned up once it is no longer the current nor previous transition (it is cleaned when it's the previous previous transition); Fixes ui-router#55 Fixes angular-ui/ui-router#3603 Fixes ui-router/angular#21
wawyed
pushed a commit
to wawyed/core
that referenced
this issue
Mar 3, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
part of ui-router/angular#21
I did some debugging and I noticed that the issue is resolved if I reset
_treeChanges
when starting a new transition in Transition::startTransitionThe text was updated successfully, but these errors were encountered: