Skip to content
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

puppeteer_dev_chrome_profile-x #295

Closed
0xDevrim opened this issue Sep 8, 2023 · 2 comments
Closed

puppeteer_dev_chrome_profile-x #295

0xDevrim opened this issue Sep 8, 2023 · 2 comments

Comments

@0xDevrim
Copy link

0xDevrim commented Sep 8, 2023

After the recent update, we've started to get hundreds of these profiles in the tmp directory which takes up the whole storage on our worker servers. There is an issue on puppeteer (puppeteer/puppeteer#6414). Is there anything we can do via decktape? Is the browser not being closed via decktape or something?

@astefanutti
Copy link
Owner

Thanks for the report. There is indeed mentions that missing browser.close() call could be the issue, but I think Decktape does that already.

There are other mention that one work-around could be do add the following parameter:

const browser = await  puppeteer.launch({
  userDataDir: '/dev/null'
});

That being said, that may likely be a regression in Puppeteer, that'll hopefully be fixed in a newer version.

@astefanutti
Copy link
Owner

This should be fixed with #321. Thanks for your patience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants