# 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:** 10

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [30 January 2025 10:03 UTC](https://discourse.nodered.org/t/nodered-crashing-due-to-javascript-out-of-heap-memory-issue/94970/10 "2025-01-30T10:03:53Z")

</div>

> [@YuktarthTrehan](#):
>
> approximately 800-1000 function nodes

Wow, ok that IS a lot!

It feels like you should be looking at how you can simplify things. 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 which is a relatively heavy task.

---

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