node-red / node-red/node-red-nodes
possible memory leak in ping node
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.1k
- Forks
- 612
- Avg merge
- 13h 57m
- Merged PRs (30d)
- 3
Description
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)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting /home/pi/.node-red/node_modules/node-red-node-ping/88-ping.js at line 30, where the stack trace shows the child process is spawned. Run the ping node repeatedly for an extended period and monitor memory and process behavior; done means the long-running ping no longer leads to ENOMEM or a Node-RED crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100