Skip to content
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

Merged
merged 1 commit into from
Jul 24, 2018

Conversation

crisbeto
Copy link
Member

Along the same lines as #12269. Clears out the mostRecentTreeNode once the last tree node is destroyed, in order to avoid a memory leak.

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.
@crisbeto crisbeto added perf This issue is related to performance target: patch This PR is targeted for the next patch release labels Jul 23, 2018
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jul 23, 2018

fixture.destroy();

expect(!!CdkTreeNode.mostRecentTreeNode).toBe(false);
Copy link
Member

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?

Copy link
Member Author

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.

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jul 24, 2018
@mmalerba mmalerba merged commit 60b9928 into angular:master Jul 24, 2018
mmalerba pushed a commit that referenced this pull request Jul 30, 2018
Along the same lines as #12269. Clears out the `mostRecentTreeNode` once the last tree node is destroyed, in order to avoid a memory leak.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement perf This issue is related to performance target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants