Developer Tools -> Detecting leaked memory by pointing out disconnected nodes
I find the Memory debugging tool good, what I am missing is to be able to see disconnected nodes easily and what is keeping them alive.
For example, these nodes may appear in the DOM Explorer colored differently in the bottom of the node tree - or in a separate section.
Then I would like to be able to click such a disconnected node and immediately see the js variable and code that keeps it alive, instead of drilling through stack traces and GC root views.
Jonathan Sampson [MSFT] commented
Hello, ewolfman. I believe this is already supported via the Memory tool you alluded to. You can see a 1, 2, 3 step image here: https://twitter.com/f12devtools/status/530795301775241216. Or were you specifically looking for a way to find detached nodes via the DOM Explorer?