reactioncommerce / reaction-cli

A command line tool for working with Reaction Commerce.
33 stars 20 forks source link

Warning: Possible EventEmitter memory leak #10

Closed aaronjudd closed 8 years ago

aaronjudd commented 8 years ago

On every upgrade I see warnings, but everything seems to still work fine. reaction runs fine, without warnings. Only reporting here, as it does happen on every upgrade and while I suspect it's outside the reaction-cli environment, it's worth tracking for a bit and investigating.

reaction/ (shipping-1320✗) $ npm i -g reaction-cli                                                                                                           [21:41:26]
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
(node:58321) Warning: Possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit
/usr/local/bin/reaction -> /usr/local/lib/node_modules/reaction-cli/dist/main.js
/usr/local/bin/rc -> /usr/local/lib/node_modules/reaction-cli/dist/main.js
/usr/local/lib
└─┬ reaction-cli@0.4.18
  ├─┬ inquirer@1.1.2
  │ └─┬ external-editor@1.0.3
  │   └─┬ spawn-sync@1.0.15
  │     └── concat-stream@1.5.2
  └─┬ update-notifier@1.0.2
    └─┬ configstore@2.1.0
      └── dot-prop@3.0.0
jshimko commented 8 years ago

I haven't seen this issue since it happened on that one day this was reported, so I'm going to assume it's all set for now.

aaronjudd commented 8 years ago

I was getting this on my last update of the CLI. I googled it this am, and found that there were some specific node versions that had this issue recently. I updated to latest node and haven't seen since. Also, was sometimes seeing this on other package installs, so I'd agree it's resolved.

jshimko commented 8 years ago

Ok, cool. Thanks for the info.