Michael Prentice

[Updated CodePen](https://codepen.io/Splaktar/pen/WzxKzd?editors=1010#0) for 1.1.7 confirms that this is still an issue.

What version of AngularJS Material is in use? Please provide a demo and reproduction steps for checking the heap and observing detached nodes. Also, are the nodes eventually garbage collected...

https://github.com/angular/material/issues/10851 also mentions that `$mdDialog` is leaking memory.

https://github.com/angular/material/issues/11493 has some additional debugging information that is related to this issue.

Here's a link to the [original CodePen](https://codepen.io/Splaktar/pen/pozLoPd) built on `1.1.8`. Here's that same CodePen [upgraded to 1.1.20](https://codepen.io/Splaktar/pen/WNezNaX). With `1.1.8` and `1.1.20`, I see the new `DialogController` instance created on the...

As for the "Detached DOM tree" mentioned above, I'm still working on finding this as it appears the Chrome DevTools have renamed these and made the Detached nodes more granular....

If I look at "Detached HTMLDivElement" in `1.1.20`, I see the following trend with heap snapshots after each open/close of the dialog: - x5 - x62 - x126 - x126...

I did a profiling run where I opened and closed the dialog every few seconds. This is the result  You can see that...

In https://github.com/angular/angular.js/issues/4864#issuecomment-29394307, it is mentioned that `ngAnimate` causes this same behavior of Nodes and listeners increasing over time, but the JS Head remaining stable. We of course do use `ngAnimate`.

 Here's a profiling session with 1.2.0 that was about 50 seconds long. You can see that, like the JS Heap, the Nodes and...