Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Dialog causes a memory leak when Dialog component contains mat-form-field
See original GitHub issueWhat is the expected behavior?
Instantiating a dialog with a component that contains mat-form-field element causes a DOM node memory leak.
What is the current behavior?
Memory leak
What are the steps to reproduce?
https://stackblitz.com/edit/angular-yx1kuw?file=app%2Fdialog-overview-example-dialog.html
Try to open and close the dialog several times. Notice each time the number of detached DOM nodes gets higher and forcing garbage collection doesn’t reduce it.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular Material: 7.3.7 Chrome: 73.0.3683.103
Is there anything else we should know?
Could be related to https://github.com/angular/material2/issues/10188
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I believe this could be the root cause issue: angular/angular/issues/25744
Should’ve been fixed in 9.0.0-rc.7 by https://github.com/angular/angular/commit/835ed0f35fa187f4051129ab30b7b635f15aeb57.