Detached DOM nodes about angular HOT 4 OPEN

I wasn't able to reproduce the issue.
Since this is not consistent, can you check that you can still reproduce it after forcing Garbage collection ?

Use the dedicated button to trigger GC:

from angular.

Hi @JeanMeche
I have tried GC but it has not collected the detached nodes.
I have tried with Edge which has a cool Detached Elements feature is its developer tools
I attach a video displaying the issue.

In the video, the first few actions, where I do not interact with the select list, are garbage collected.
As soon as I select something in the list, the whole component is detached and not garbage collected

Let me know if you need any more information
Thanks

from angular.

Continuing from the previous video, I attach a new one, where following the details described in Microsoft's article on detached nodes,
https://learn.microsoft.com/en-us/microsoft-edge/devtools-guide-chromium/memory-problems/dom-leaks#identify-the-dom-node-causing-others-to-be-retained,
the Detached Elements functionality of their Dev Tools, has the ability to pinpoint the exact culprit, by breaking the parent child DOM graph

So, stripping the DOM, the culprit seems to be the select DOM element

Hope this helps

from angular.

Back again with another observation.
I would expect the detached elements to keep increasing, once you enter the view, interact with the select element and return to the home page.
However this is not true and also puzzling.
Instead, as shown in the below video, the ,app-list> that remains detached, seems to be collected and replaced by a new one, each time you execute the beforementioned actions.
I have tried both with zone and zoneless and the behavior is the same.
Hope the above help

from angular.