(node:36029) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit

LucianoGanga / simple-headless-chrome

Simple abstraction to use Chrome as a Headless Browser with Node JS

MIT License

217 stars 50 forks source link

(node:36029) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit #72

Closed Tin-Nguyen closed 7 years ago

Tin-Nguyen commented 7 years ago

Hi all,

I got the issue every time with high-load print to PDF using simple-headless-chrome.

(node:36029) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit

Please check if it's an issue of the lib

LucianoGanga commented 7 years ago

Hi!

That happened to me when running many instances in the same machine. I fix it by distributing the time between the launch of new chrome instances.

I know it's not the "final" solution, but maybe it gives you some idea about what's generating that on your computer.

Cheers! Lucho

Tin-Nguyen commented 7 years ago

Hi @LucianoGanga , thanks for your working on this issue. I will try to upgrade the latest version of simple-headless-chrome and check the issue.

However, I'm wondering your found issue is the same as my issue or not, since I'm using an existing Chrome instance in Docker and remotely connect my service to it. Thoughts?