node: possible EventEmitter memory leak detected. #9

Closed
kvervo opened this Issue Nov 25, 2013 · 1 comment

Comments

Projects
None yet
2 participants
@kvervo

kvervo commented Nov 25, 2013

I have been trying to solve this issue:
yeoman/node-gifsicle#11 (comment)

When trying to build on the build server I get the following warning:

[Step 1/1] (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.
[20:45:23][Step 1/1] Trace
[20:45:23][Step 1/1]     at IncomingMessage.EventEmitter.addListener (events.js:160:15)
[20:45:23][Step 1/1]     at Through2.<anonymous> (/root/BuildAgent/work/443e455e9b41081f/node_modules/grunt-contrib-imagemin/node_modules/jpegtran-bin/node_modules/bin-wrapper/bin-wrapper.js:124:13)
[20:45:23][Step 1/1]     at Through2.EventEmitter.emit (events.js:117:20)
[20:45:23][Step 1/1]     at Request.<anonymous> (/root/BuildAgent/work/443e455e9b41081f/node_modules/grunt-contrib-imagemin/node_modules/jpegtran-bin/node_modules/bin-wrapper/node_modules/download/download.js:37:20)
[20:45:23][Step 1/1]     at Request.EventEmitter.emit (events.js:117:20)
[20:45:23][Step 1/1]     at Request.onResponse (/root/BuildAgent/work/443e455e9b41081f/node_modules/grunt-contrib-imagemin/node_modules/jpegtran-bin/node_modules/bin-wrapper/node_modules/download/node_modules/request/index.js:830:10)
[20:45:23][Step 1/1]     at ClientRequest.g (events.js:175:14)
[20:45:23][Step 1/1]     at ClientRequest.EventEmitter.emit (events.js:95:17)
[20:45:23][Step 1/1]     at HTTPParser.parserOnIncomingClient [as onIncoming] (http.js:1688:21)
[20:45:23][Step 1/1]     at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:121:23)

I believe there is an issues with the event emitter that is why on yeoman/node-gifsicle#11 (comment) we get looping downloads.

@kvervo kvervo closed this Nov 25, 2013

@kvervo

This comment has been minimized.

Show comment Hide comment
@kvervo

kvervo Nov 25, 2013

@kvervo kvervo reopened this Nov 25, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment