# Memory of nodered app not coming down

**URL:** <https://discourse.nodered.org/t/memory-of-nodered-app-not-coming-down/25286>\
**Category:** Dashboard\
**Created:** [22 April 2020 06:46 UTC](https://discourse.nodered.org/t/memory-of-nodered-app-not-coming-down/25286 "2020-04-22T06:46:13Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [28 April 2020 07:00 UTC](https://discourse.nodered.org/t/memory-of-nodered-app-not-coming-down/25286/4 "2020-04-28T07:00:13Z")

</div>

> [@SiddharthJoshi](#):
>
> Is there any way to know the node/flow which is causing leak?

Hi Siddharth,  
Some time ago I have "tried" to create a contribution for Node-RED that allowed us to list the memory usage of every node, in order to quickly determine where the problem is located.  
However after the feedback I got on this forum, it appeared to be impossible. On the [readme](https://github.com/bartbutenaers/node-red-contrib-nodes-memory) you can see in the section "Limitations" _ **why** _ I had to quit this contribution at the time being...

---

_[View the full topic](https://discourse.nodered.org/t/memory-of-nodered-app-not-coming-down/25286)._