-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
possible memory leak in ping node #170
Comments
how was this running ? Is this on Pi... |
yes, on Pi, with --max-old-space-size=256 |
Slightly tricky one this... |
I'm wondering why it would have got this error, though - when it crashed, I was able to log in and do stuff on the Pi, so it evidently wasn't out of system memory... |
Not sure if this is relevant but I am beginning to suspect that this ping node is crashing my pi 3. It's been running Node-red fine for ages. About 2 weeks ago I added some new custom nodes and since then the Pi has been becoming unresponsive and requiring power cycling (no response to ssh, does not serve any pages from node red) A few days ago I removed all the new nodes other than ping but pi was still dying. Today I investigated a bit more. 20 minutes after the pi boots the node process jumps to the top of cpu usage with 100% (or over) usage. |
Nope, not the ping node. Still dying after removing it. |
How are you staying Node-RED. Does indeed sound like it's running out of
memory. But 20 mins is very quick. What is the flow doing ?
|
The flow is pretty complex but it's just for controlling my lights. I have Hue nodes and wemo nodes that are kicked off with http request nodes. Most of the time it is doing nothing (unless I call one of the http nodes). |
@dceejay didn't think about rewriting to use https://www.npmjs.com/package/net-ping ? in docker after ~ 1 week work a see many process ping and error
and container Node-Red use more cpu / memory |
No - but more than happy to look at a Pull Request. |
for history not good idea use net-ping for this node, in install host windows . not easy compiled / install net-ping ... (it worked for me on win10/server 2016/server 2019, but it didn’t work on win7) |
ah - right - so it uses a binary and not pure JS... then yeah not such a great solution :-( |
After a long time (weeks) of pinging every 15 seconds, Node-RED crashed with:
26 Jan 12:46:45 - [red] Uncaught Exception:
26 Jan 12:46:45 - Error: spawn ENOMEM
at exports._errnoException (util.js:746:11)
at ChildProcess.spawn (child_process.js:1162:11)
at exports.spawn (child_process.js:995:9)
at null. (/home/pi/.node-red/node_modules/node-red-node-ping/88-ping.js:30:41)
at wrapper as _onTimeout
at Timer.listOnTimeout (timers.js:119:15)
The text was updated successfully, but these errors were encountered: