# NodeRED crashing due to "Javascript out of heap memory" issue

**URL:** https://discourse.nodered.org/t/nodered-crashing-due-to-javascript-out-of-heap-memory-issue/94970
**Category:** General
**Tags:** docker
**Created:** [29 January 2025 05:47 UTC](https://discourse.nodered.org/t/nodered-crashing-due-to-javascript-out-of-heap-memory-issue/94970 "2025-01-29T05:47:48Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)
#### Post date: [30 January 2025 13:25 UTC](https://discourse.nodered.org/t/nodered-crashing-due-to-javascript-out-of-heap-memory-issue/94970/14 "2025-01-30T13:25:09Z")

</div>

> [@TotallyInformation](#):
>
> Also, with that number of nodes, take care with debug nodes and places in your flows where you have \>1 wire connected to the output of a node. That's because having multiple wires on an output causes Node-RED to have to CLONE the output messages

Is that true if the wire goes to a disabled node?  
What about a debug node whose output is "turned off"?

> [@YuktarthTrehan](#):
>
> Multiple flows are involved, including both active and disabled ones, interacting with different data sources, including InfluxDB instances and Modbus clients.

Does this Node-red instance interact directly with database and Modbus clients?  
It might be worth moving data acquisition to a separate NR instance on another machine and use MQTT to forward it to be processed.

What hardware are you running on?

Have you experimented with the same Node-red flows but not under Docker? (I have no reason at all to think Docker might be at fault, it's just one more factor to consider).

[This thread](This thread [[Question about context and RAM - #2 by Paul-Reed](https://discourse.nodered.org/t/question-about-context-and-ram/47068/2)]) discusses some ways to monitor Node-red memory usage.

---

_[View the full topic](https://discourse.nodered.org/t/nodered-crashing-due-to-javascript-out-of-heap-memory-issue/94970)._