-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
perf(tree): leaking reference through mostRecentTreeNode #12334
perf(tree): leaking reference through mostRecentTreeNode #12334
Conversation
Along the same lines as angular#12269. Clears out the `mostRecentTreeNode` once the last tree node is destroyed, in order to avoid a memory leak.
|
||
fixture.destroy(); | ||
|
||
expect(!!CdkTreeNode.mostRecentTreeNode).toBe(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just toBeFalsy
or toBeNull
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a comment about it a few lines about. Using .toBeFalsy
will cause Jasmine to go into an infinite loop, if this test ever starts failing, because it tries to stringify an object with circular references.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Along the same lines as #12269. Clears out the `mostRecentTreeNode` once the last tree node is destroyed, in order to avoid a memory leak.
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. |
Along the same lines as #12269. Clears out the
mostRecentTreeNode
once the last tree node is destroyed, in order to avoid a memory leak.