search

erming / shout

Deprecated. See fork @ https://github.com/thelounge
MIT License
3.62k stars 272 forks source link

Possible EventEmitter memory leak detected #557

Open Henni opened 8 years ago

Henni commented 8 years ago

I just found this in my logs. Even though my server didn't crash, it may be a first sign, that it will soon crash:

(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at Request.EventEmitter.addListener (events.js:160:15)
    at Request.start (/usr/local/lib/node_modules/shout/node_modules/request/request.js:843:8)
    at Request.end (/usr/local/lib/node_modules/shout/node_modules/request/request.js:1400:10)
    at end (/usr/local/lib/node_modules/shout/node_modules/request/request.js:564:14)
    at Object._onImmediate (/usr/local/lib/node_modules/shout/node_modules/request/request.js:578:7)
    at processImmediate [as _immediateCallback] (timers.js:330:15)
(node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
    at Request.EventEmitter.addListener (events.js:160:15)
    at Request.init (/usr/local/lib/node_modules/shout/node_modules/request/request.js:496:8)
    at Redirect.onResponse (/usr/local/lib/node_modules/shout/node_modules/request/lib/redirect.js:149:11)
    at Request.onRequestResponse (/usr/local/lib/node_modules/shout/node_modules/request/request.js:944:22)
    at ClientRequest.EventEmitter.emit (events.js:95:17)
    at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1688:21)
    at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)
    at Socket.socketOnData [as ondata] (http.js:1583:20)
    at TCP.onread (net.js:525:27)