# How would I find a "memory leak"?

**URL:** <https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806>\
**Category:** General\
**Created:** [20 September 2026 09:43 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806 "2026-09-20T09:43:17Z")\
**Posts on this page:** 6\
**Page:** 3

<div class="post-metadata">

**Author:** ![nlecaude](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/nlecaude/32/25_2.png) [@nlecaude](https://discourse.nodered.org/u/nlecaude)\
**Post date:** [20 September 2026 22:21 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806/41 "2026-09-20T22:21:34Z")

</div>

If it’s Node-RED leaking I usually use this node [node-red-contrib-heap-dump (node) - Node-RED](https://flows.nodered.org/node/node-red-contrib-heap-dump)  
To take memory snapshots at different intervals, I then analyse it with the chrome debugger tools.  
Nowadays you can probably throw the snapshot files at an LLM that should be able to analyse it quickly.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [20 September 2026 22:29 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806/42 "2026-09-20T22:29:13Z")

</div>

I'll give that a try.

Thanks.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [25 September 2026 21:14 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806/43 "2026-09-25T21:14:32Z")

</div>

Well, if anyone is still reading this:

The full reboot got the used memory down to (can't remember exactly and for some reason can't find the numbers I posted) about 44%

It's now been 4 days and it flat at 46%.

😕

So it is (or seems to be) happy now.

The node mentioned:  
It crashes NR.

But that MAY be because it is 4.0.9  
🤷

Thanks all who posted/helped.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [2 October 2026 07:18 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806/44 "2026-10-02T07:18:06Z")

</div>

1 week 4 days uptime.

49% memory used.

So what ever it is/was: It's gone now.

Thanks folks.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [2 October 2026 08:03 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806/45 "2026-10-02T08:03:17Z")

</div>

As you could see from some of the earliest screenshots of `top` it was lxpanel causing the issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [16 October 2026 08:03 UTC](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806/46 "2026-10-16T08:03:45Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

[Previous page](https://discourse.nodered.org/t/how-would-i-find-a-memory-leak/101806.md?page=2)