{"action":"created","issue":{"url":"https://api.github.com/repos/npm/npm/issues/13806","repository_url":"https://api.github.com/repos/npm/npm","labels_url":"https://api.github.com/repos/npm/npm/issues/13806/labels{/name}","comments_url":"https://api.github.com/repos/npm/npm/issues/13806/comments","events_url":"https://api.github.com/repos/npm/npm/issues/13806/events","html_url":"https://github.com/npm/npm/issues/13806","id":173963729,"number":13806,"title":"\"possible EventEmitter memory leak detected.\" warning during npm install","user":{"login":"markvincze","id":1122274,"avatar_url":"https://avatars.githubusercontent.com/u/1122274?v=3","gravatar_id":"","url":"https://api.github.com/users/markvincze","html_url":"https://github.com/markvincze","followers_url":"https://api.github.com/users/markvincze/followers","following_url":"https://api.github.com/users/markvincze/following{/other_user}","gists_url":"https://api.github.com/users/markvincze/gists{/gist_id}","starred_url":"https://api.github.com/users/markvincze/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markvincze/subscriptions","organizations_url":"https://api.github.com/users/markvincze/orgs","repos_url":"https://api.github.com/users/markvincze/repos","events_url":"https://api.github.com/users/markvincze/events{/privacy}","received_events_url":"https://api.github.com/users/markvincze/received_events","type":"User","site_admin":false},"labels":[{"id":104304843,"url":"https://api.github.com/repos/npm/npm/labels/support","name":"support","color":"000000","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":26,"created_at":"2016-08-30T08:52:11Z","updated_at":"2016-12-20T21:29:16Z","closed_at":"2016-08-30T14:12:08Z","body":"### I'm opening this issue because:\n- [ ] npm is producing a concerning warning during `npm install`.\n### What's going wrong?\n\nDuring `npm install` I get several of the following warning message:\n\n```\n(node) warning: possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit.\nTrace\n    at TLSSocket.addListener (events.js:239:17)\n    at TLSSocket.Readable.on (_stream_readable.js:680:33)\n    at Request.<anonymous> (/home/mvincze/.nvm/versions/node/v4.4.7/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:153:7)\n    at emitOne (events.js:77:13)\n    at Request.emit (events.js:169:7)\n    at ClientRequest.<anonymous> (/home/mvincze/.nvm/versions/node/v4.4.7/lib/node_modules/npm/node_modules/request/request.js:791:10)\n    at emitOne (events.js:82:20)\n    at ClientRequest.emit (events.js:169:7)\n    at tickOnSocket (_http_client.js:502:7)\n    at onSocketNT (_http_client.js:514:5)\n```\n\nTo me this is happening with `2.15.10`. I haven't pinpointed the particular version this started happening with, but it doesn't happen with `2.10`.\n### How can the CLI team reproduce the problem?\n\nI'd expect this to be happening with many repositories, one example is https://github.com/Travix-International/frint.\nSimply clone the repo and do `npm install` with npm version `2.15.10`.\n### Supporting information:\n- `npm -v` prints: 2.15.10\n- `node -v` prints: v4.4.7\n- `npm config get registry` prints: https://registry.npmjs.org/\n- Windows, OS X, or Linux?: Linux\n\nBtw. I tried to google this problem, and found a couple of threads, but they were related to earlier versions of npm, so this might be a regression.\n"},"comment":{"url":"https://api.github.com/repos/npm/npm/issues/comments/268364705","html_url":"https://github.com/npm/npm/issues/13806#issuecomment-268364705","issue_url":"https://api.github.com/repos/npm/npm/issues/13806","id":268364705,"user":{"login":"KenanY","id":733364,"avatar_url":"https://avatars.githubusercontent.com/u/733364?v=3","gravatar_id":"","url":"https://api.github.com/users/KenanY","html_url":"https://github.com/KenanY","followers_url":"https://api.github.com/users/KenanY/followers","following_url":"https://api.github.com/users/KenanY/following{/other_user}","gists_url":"https://api.github.com/users/KenanY/gists{/gist_id}","starred_url":"https://api.github.com/users/KenanY/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KenanY/subscriptions","organizations_url":"https://api.github.com/users/KenanY/orgs","repos_url":"https://api.github.com/users/KenanY/repos","events_url":"https://api.github.com/users/KenanY/events{/privacy}","received_events_url":"https://api.github.com/users/KenanY/received_events","type":"User","site_admin":false},"created_at":"2016-12-20T21:29:15Z","updated_at":"2016-12-20T21:29:15Z","body":"@jali I see `npm@3.10.8` in the registry just fine; it's been there for quite some time now. Even if you don't see it for whatever reason, you could always install an even newer version of `npm`.\r\n\r\n@gitdang Are you sure that what you're seeing is an issue with `npm` specifically? If so, feel free to open a new issue with some steps to reproduce :), otherwise it's a bit more likely that it's the fault of your own code :("}}
{"actor":{"display_login":"KenanY"}}