# This is an interesting error (ENOMEM) Help anyone?

**URL:** <https://discourse.nodered.org/t/this-is-an-interesting-error-enomem-help-anyone/26977>\
**Category:** General\
**Created:** [20 May 2020 08:14 UTC](https://discourse.nodered.org/t/this-is-an-interesting-error-enomem-help-anyone/26977 "2020-05-20T08:14:23Z")\
**Posts on this page:** 4\
**Page:** 1

<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 May 2020 08:14 UTC](https://discourse.nodered.org/t/this-is-an-interesting-error-enomem-help-anyone/26977/1 "2020-05-20T08:14:24Z")

</div>

I kind of mentioned it earlier, but I didn't see it this bad and I'm not sure it is the same problem or just the original's bigger brother.

Can anyone help me understand if this is a nasty problem?

```auto
Error: spawn ENOMEM at ChildProcess.spawn (internal/child_process.js:313:11) at exports.spawn (child_process.js:508:9) at Object.exports.execFile (child_process.js:218:15) at Object.exports.exec (child_process.js:148:18) at VcGenCmdNode._inputCallback (/home/pi/.node-red/node_modules/node-red-contrib-vcgencmd/vcgencmd.js:106:47) at VcGenCmdNode.Node._emitInput (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:199:18) at Immediate.<anonymous> (/usr/lib/node_modules/node-red/node_modules/@node-red/runtime/lib/nodes/Node.js:179:33) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5)

```

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [20 May 2020 08:21 UTC](https://discourse.nodered.org/t/this-is-an-interesting-error-enomem-help-anyone/26977/2 "2020-05-20T08:21:45Z")

</div>

you are out of memory - so yes - it's a problem as it is likely to crash soon unless resolved.

---

<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 May 2020 08:24 UTC](https://discourse.nodered.org/t/this-is-an-interesting-error-enomem-help-anyone/26977/3 "2020-05-20T08:24:03Z")

</div>

Soon.. 😉 It keeps.

Drats.

What may not have been helping was I have/had **two** of the nodes on the same machine.

I have just re-written it and it now only uses one.

That may help.

---

<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:** [19 July 2020 08:29 UTC](https://discourse.nodered.org/t/this-is-an-interesting-error-enomem-help-anyone/26977/4 "2020-07-19T08:29:15Z")

</div>

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