How Chrome ate 21GB of storage
blog.francoismaillet.com
How Chrome ate 21GB of storage
1–10 of 81 posts
Re: How Chrome ate 21GB of storage
#2This just seems like something that should've been fixed years ago
Re: How Chrome ate 21GB of storage
#3I'm going to post a theory that with 500Gb drives pretty much the normal size that most people won't notice 2.5% tied up in Chrome installs.
Re: How Chrome ate 21GB of storage
#4I'm going to post a theory that with 500Gb drives pretty much the normal size that most people won't notice 2.5% tied up in Chrome installs.
Except if you've bought a Lenovo 100s or similar, with 32GB of eMMC Flash storage. Then you'll cry.
Re: How Chrome ate 21GB of storage
#5Does this only occur on Macs?
Re: How Chrome ate 21GB of storage
#6This is embarrassingly bad. I know memory is cheap and mostly plentiful, but to have this as a bug for 5+ years is horrible. It's as though Chrome is going the route of web pages and not paying to the size of itself.
Re: How Chrome ate 21GB of storage
#7This is embarrassingly bad. I know memory is cheap and mostly plentiful, but to have this as a bug for 5+ years is horrible. It's as though Chrome is going the route of web pages and not paying to the size of itself.
This is prior versions of Chrome taking up disk space, not memory. That's a completely separate issue.
Re: How Chrome ate 21GB of storage
#8I feel like it's slightly dishonest not to mention that (according to the Chrome devs) this problem is caused by poorly-behaved modifications to the Chrome installer made by third-party redistributors, and not by Chrome itself.
(Disclosure: I work for Google, but not on Chrome.)
Re: How Chrome ate 21GB of storage
#9I installed mine through Homebrew (http://brew.sh/) Cask (https://caskroom.github.io/) and it is fine (only last two versions).
Re: How Chrome ate 21GB of storage
#10This is embarrassingly bad. I know memory is cheap and mostly plentiful, but to have this as a bug for 5+ years is horrible. It's as though Chrome is going the route of web pages and not paying to the size of itself.
Embarrassing, obvious, multi-year bugs are common to all browsers though. In Firefox, bookmarklets on CSP pages have been broken for 3.5 years and counting, with the end nowhere in sight. A handful of bugs that have taken a while to fix is no way to judge the overall quality of the browser.