Skip to content
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

Crashes if too many publishes occur #1

Closed
adamvr opened this issue Feb 13, 2012 · 1 comment
Closed

Crashes if too many publishes occur #1

adamvr opened this issue Feb 13, 2012 · 1 comment

Comments

@adamvr
Copy link
Owner

adamvr commented Feb 13, 2012

node-growl spawns a new growlnotify process for each notification and if we get a whole heap of publishes it tends to hit the process limit.

child_process.js:477
    throw errnoException(errno, 'spawn');
    ^
Error: spawn EMFILE
    at errnoException (child_process.js:514:11)
    at ChildProcess.spawn (child_process.js:477:11)
    at child_process.js:375:9
    at Object.execFile (child_process.js:285:15)
    at child_process.js:252:18
    at growl (/usr/local/lib/node_modules/mqtt-growl/node_modules/growl/lib/growl.js:187:3)
    at Connection.<anonymous> (/usr/local/lib/node_modules/mqtt-growl/mqtt-growl:64:9)
    at Connection.emit (events.js:67:17)
    at Connection.parse (/usr/local/lib/node_modules/mqtt-growl/node_modules/mqttjs/lib/connection.js:108:9)
    at Socket.emit (events.js:67:17)

Consider migrating to something that has a persistent connection to the growl server or throttle node-growl somehow.

Suggestions:

https://github.com/betamos/Node-Growler

@adamvr
Copy link
Owner Author

adamvr commented Jun 3, 2012

Stopgap solution implemented with -d parameter. Still not really good enough.

@adamvr adamvr closed this as completed Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant