-
-
Notifications
You must be signed in to change notification settings - Fork 745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zombie process killing memory and cpu #377
Comments
ashvin777
changed the title
Zombies process killing memory and cpu
Zombie process killing memory and cpu
Oct 5, 2019
Most likely a Puppeteer issue. You might find some useful info here: puppeteer/puppeteer#1825 |
Can't you try something like this to see if you have any zombie instances of Pageres and/or Chrome?
|
Try the latest version: https://github.com/sindresorhus/pageres/releases/tag/v7.0.0 It may have resolved the issue. |
Thank you... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using Pageres to generate snapshots for the HTML snippets on my server. As soon as some request for the snapshot, I am executing
new Pageres(...).src(..).dest(..).run(..)
and it does generate screenshot and saves it. However the chrome instance still remain in my processes which is eating up complete memory and cpu eventually. Is there any handling which we can do to control this behaviour ? It was also creating somedefunct
(zombies) process as well which I am killing in an interval using a NodeJS script already, but I can't kill these because they might be doing something at that moment of time.Also the process doesn't respond if any page contains
alert
in it.The text was updated successfully, but these errors were encountered: