Chrome zombie process on Ubuntu
See original GitHub issue- 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
Issue Analytics
- State:
- Created 4 years ago
- Reactions:11
- Comments:14
Top Results From Across the Web
How to Kill Zombie Processes in Ubuntu - VITUX
Open the System Monitor utility through Ubuntu Dash. Search for the term Zombie through the Search button. Select the zombie process, right- ...
Read more >Chrome exits leaving zombies. Zombies interfere with starting ...
1. Boot up machine. 2. Check for Chrome zombies: none (0) found. 3. Start Chrome browser. Timeout occurs: Wait, Kill, "It's dead, Jim!"...
Read more >How to kill zombie processes in Ubuntu 18.04 - Ubunlog
Small tutorial or tip on how to locate zombie processes within our Ubuntu 18.04 and kill them so that it works correctly ......
Read more >How to identify and kill zombie/defunct processes in Linux ...
1) Identify the zombie processes. top -b1 -n1 | grep Z · 2) Find the parent of zombie processes · 3) Send SIGCHLD...
Read more >How to Kill Zombie Processes on Linux - How-To Geek
What Causes Zombie Processes on Linux? ... A poorly written parent process might not call the wait() function when the child process is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.
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!