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
ReLaXed spawns defunct chrome processes #137
Comments
Hi @jonathanasquier, the https://github.com/RelaxedJS/ReLaXed/blob/master/src/index.js#L142-L143
Currently I see no usage of Can you try to add |
I tried, with no success :(
which prevent ending up with defunct chrome processes If you believe this issue/solution is out of scope of the ReLaXed project, feel free to close it :) |
Right, sounds like this issue. But I'm not completely sure if we should still properly close the browser instances. |
Hi,
I'm using relaxed in nodeJS with a promise interface by spawning a relaxed child process.
I recently crashed my production server with 32k+ defunct chrome processes.
I tried to
tree-kill
my own child process,browser.close()
andtree-kill
theprocess.pid
in theprogram.buildOnce
condition, but still it seems 4-5 chrome process are launched.Right now the only way I've got to prevent my server from crashing is restarting my docker container every once and a while, which destroys the chrome processes (I'm the one who wrote the dockerfile that is referenced in ReLaXed's README :) )
I have no experience with working directly with puppeteer and would be delighted with a little help!
Thanks!
PS: please don't let me use wkhtmltopdf again!!
The text was updated successfully, but these errors were encountered: