MaxListenersExceededWarning: Possible EventEmitter memory leak detected about puppeteer-cluster

[thomasdondorf]

Thanks for reporting, this definitely needs investigation.

[hashtafak]

On each launch() function called, 4 events have been adding to NodeJS's process

const listeners = [helper.addEventListener(process, 'exit', killChrome)];
if (handleSIGINT)
    listeners.push(helper.addEventListener(process, 'SIGINT', () => {
        killChrome();
        process.exit(130);
    }));
if (handleSIGTERM)
    listeners.push(helper.addEventListener(process, 'SIGTERM', gracefullyCloseChrome));
if (handleSIGHUP)
    listeners.push(helper.addEventListener(process, 'SIGHUP', gracefullyCloseChrome));

When puppeteer-cluster launch a lot of Worker, NodeJS will show MaxListenersExceededWarning error

FYI: https://nodejs.org/api/events.html#events_eventemitter_defaultmaxlisteners

By default, a maximum of 10 listeners can be registered for any single event.
.. EventEmitters will print a warning if more than 10 listeners are added for a particular event. This is a useful default that helps finding memory leaks.

You can easily disable this warning by using process.setMaxListeners(n) with n=20 in your case or more.

puppeteer/puppeteer#594

For advanced use, you can remove all event listeners exit added by Puppeteer. And do some stuff like killChrome() and gracefullyCloseChrome() by yourself.

Note that 3 events SIGINT, SIGTERM, SIGHUP can be disabled in launch() options. Work in my case

const browser = await puppeteer.launch({
    handleSIGINT = false,
    handleSIGTERM = false,
    handleSIGHUP = false,
});

[bangbambang]

Note that 3 events SIGINT, SIGTERM, SIGHUP can be disabled in launch() options. Work in my case

const browser = await puppeteer.launch({
    handleSIGINT = false,
    handleSIGTERM = false,
    handleSIGHUP = false,
});

FYI, most process managers use at least one of those signals to "ask" the process to terminate nicely. For example, systemd would send SIGTERM followed by SIGINT 90 seconds later (default behavior). Disabling them without explicitly call killChrome or gracefullyCloseChrome may spawn zombie processes.

raising max listeners to match worker count would be the safest workaround. As an added bonus, you could register additional listeners to do resource cleanup when the signal received.

[mastershaig]

For me removing '--single-process', from args fixed the issue

puppeteerOptions: {
    headless: true,
    args: [
        // '--single-process',
    ],
}