Chrome zombie process on Ubuntu

• Puppeteer version: 1.19.0
• Platform / OS version: Windows 10, Ubuntu 16
• URLs (if applicable):
• Node.js version: 12.13.1

The memory leak issue is caused by the chrome zombie process as shown below. Clearly, I closed the page and browser.

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:33268         0.0.0.0:*               LISTEN      16312/chrome
tcp        0      0 127.0.0.1:44663         0.0.0.0:*               LISTEN      6967/chrome
tcp        0      0 127.0.0.1:42206         0.0.0.0:*               LISTEN      13966/chrome
tcp        0      0 0.0.0.0:10022           0.0.0.0:*               LISTEN      1239/sshd
tcp        0      0 127.0.0.1:41864         0.0.0.0:*               LISTEN      4205/chrome
tcp        0      0 127.0.0.1:35405         0.0.0.0:*               LISTEN      5656/chrome
tcp        0      0 127.0.0.1:40624         0.0.0.0:*               LISTEN      4286/chrome
tcp6       0      0 :::3030                 :::*                    LISTEN      2597/index.js
tcp6       0      0 :::10022                :::*                    LISTEN      1239/sshd

await browser.close() works fine on windows, but on Linux it does not work intermittently, resulting in numerous zombie processes. So a memory leak occurred.

So, after using browser.disconnect() instead of browser.close(), I tried to handle it using the event listener as shown below. But it doesn’t seem to work at all. console.log () is not printed.

browser.disconnect()
browser.on('disconnected', () => console.log('disconnected'))

If you have dprecated api please tell me.

=========== Reference: #1825

[alexellis]

https://github.com/buildkite/docker-puppeteer/issues/142

And the repo

https://github.com/alexellis/openfaas-puppeteer-template

If you’re interested in using faasd there’s a blog post linked to it and it supports queuing and running on a low spec VPS too.

[stale[bot]]

We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it!