{"issue":{"created_at":"2011-11-11T18:49:05Z","state":"open","updated_at":"2011-11-29T22:09:10Z","comments":11,"user":{"gravatar_id":"5a75c168270e3ac99733fc3905066d03","id":673922,"url":"https://api.github.com/users/sethml","login":"sethml","avatar_url":"https://secure.gravatar.com/avatar/5a75c168270e3ac99733fc3905066d03?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"Fixed problem: When a keep-alive connection has many requests, each request can result in a separate bounce, and all of those bounces getting piped back into the request stream can result in ugly warnings on stdout:\r\n\r\n```\r\n  (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit.\r\n  Trace:\r\n      at Socket.<anonymous> (events.js:126:17)\r\n      at Socket.pipe (stream.js:156:8)\r\n      at /Users/seth/development/service/node_modules/bouncy/index.js:86:20\r\n      at /Users/seth/development/service/scalar.js:52:5\r\n      at IncomingMessage.onHeaders (/Users/seth/development/service/node_modules/bouncy/index.js:46:13)\r\n      at IncomingMessage.emit (events.js:64:17)\r\n      at Parser.<anonymous> (/Users/seth/development/service/node_modules/bouncy/node_modules/parsley/lib/modes.js:135:21)\r\n      at Parser.execute (/Users/seth/development/service/node_modules/bouncy/node_modules/parsley/index.js:20:35)\r\n      at Socket.<anonymous> (/Users/seth/development/service/node_modules/bouncy/node_modules/parsley/index.js:11:14)\r\n      at Socket.emit (events.js:64:17)\r\n```","assignee":null,"id":2212217,"pull_request":{"patch_url":"https://github.com/substack/bouncy/pull/11.patch","html_url":"https://github.com/substack/bouncy/pull/11","diff_url":"https://github.com/substack/bouncy/pull/11.diff"},"number":11,"labels":[],"title":"Avoid 'EventEmitter memory leak' warnings.","closed_at":null,"html_url":"https://github.com/substack/bouncy/issues/11","url":"https://api.github.com/repos/substack/bouncy/issues/11","milestone":null},"action":"created","comment":{"created_at":"2011-11-29T22:09:10Z","updated_at":"2011-11-29T22:09:10Z","user":{"gravatar_id":"7972c616246ab60df7cbc374d4ef9d35","id":70011,"url":"https://api.github.com/users/Marak","login":"Marak","avatar_url":"https://secure.gravatar.com/avatar/7972c616246ab60df7cbc374d4ef9d35?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png"},"body":"It's impossible to say with your testing scenario. You can't get accurate results using the same machine / host for client and server. You also might have some something misconfigured something or your testing code might not test what you think it does. Too many unknown variables.\r\n\r\nIf you want to understand the cause of the issue, you can try opening up a support issue on the `http-proxy` repo.\r\n\r\n","id":2951326,"url":"https://api.github.com/repos/substack/bouncy/issues/comments/2951326"}}