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
What's going on with Chromium size, it has grown three times in the latest minor release (1.17.0 -> 1.18.0) #4610
Comments
Yeah, I was wondering the same thing. Redeploying something using Puppeteer and Chromium is now over one-third of a GB in size |
Whoa, that's a bug! |
Thank you @aslushnikov! As I can see the reported issue is already fixed. I have an offtopic question: since you work in Google do you maybe know why isn't Chromium repo on Github? I mean GitHub is the "default" place to collaborate on software. The current UI for Chromium's bug-tracker looks terrible (in my eyes) and I personally can't figure out what's happening with repo and therefore can't contribute. |
It's been running Travis CI out of memory too. Reverting to |
It also is causing slug sizes on Heroku to be too large if you run puppeteer there. Confirm that reverting to |
This roll includes: - https://crrev.com/671499 - Build with symbol_level=0 for linux-archive-rel Fix puppeteer#4610
This roll includes: - https://crrev.com/671499 - Build with symbol_level=0 for linux-archive-rel Fix #4610
Same issue, reverting to |
We released v1.18.1 with the fix for the bug. Sorry for this regression! |
I'm trying to install
puppeteer
on Linux and was shocked by the Chromium size:Is Chromium growing so rapidly or is it a bug?
The text was updated successfully, but these errors were encountered: