# Detached DOM tree memory leak

**URL:** <https://community.cesium.com/t/detached-dom-tree-memory-leak/10274>\
**Category:** CesiumJS\
**Created:** [July 20, 2020, 6:35am UTC](https://community.cesium.com/t/detached-dom-tree-memory-leak/10274 "2020-07-20T06:35:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Baruch\_Levin](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/baruch_levin/32/2400_2.png) [@Baruch\_Levin](https://community.cesium.com/u/Baruch_Levin)\
**Post date:** [July 20, 2020, 6:35am UTC](https://community.cesium.com/t/detached-dom-tree-memory-leak/10274/1 "2020-07-20T06:35:18Z")

</div>

Hello,  
I want to analyze why in my angular application i have a “detached DOM tree memory leak”.

I use pure cesium js, not “angular cesium”.

I removed the map from angular and still see the same “detached…”.

I go to devtools, and then to memory, choose “heap snapshot”, press “take snapshot”.

After it finished, near the “summary” there is “class filter”. I wrote there detached, and i see that cesium and knockout make this memory leak.

I use cesium version: 1.70.1

Thanks in advance.