Live data from Hacker News

How Chrome ate 21GB of storage

blog.francoismaillet.com

51–60 of 81 posts

Re: How Chrome ate 21GB of storage

#51

I 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.)

dishonesty averted! He added a disclosure. :-)

Re: How Chrome ate 21GB of storage

#52
post #49
post #15

Earlier quoted context omitted.

> I 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. What do you mean ? if I download Chrome from the official website I get a third party installer ? because I have the exact same problem with that very official installer.

It looks like the linked article has been updated at the end to clarify. It sounds like some third party extension's installer (e.g. DivX) is reaching into Chrome.app and mucking with permissions (setting owner to root). Not sure why they don't install into "/Library/Internet Plug-Ins" (maybe it doesn't work with chrome anymore?) (Edit: but a comment in the linked bug report suggests that this may also occur if Chrom…

The bug report claims that in the different-user case you do get a privilege escalation prompt.

Re: How Chrome ate 21GB of storage

#53

Earlier quoted context omitted.

Even with 1TB disk space I'm resentful of the amount of space "leaked" by software. Maybe I'm a naz-, maybe I was born in the MB era.. can't say. The other day I booted a P3 era machine and seeing all we did with "just" 128MB made me feel chills all over.

I blame the perpetual-beta mentality along with lazy development practices. Used to be, we specced out exactly what was in a release and no more. Now, it's just whatever they can cram in under a deadline without all that "unnecessary" optimization. I'm probably as guilty as anyone else; I like getting a paycheck and so I keep my mouth shut, even though shit like that literally keeps me up some nights.

I see a few reasons: less compiled languages, more abstractions, more best practices, that means a lot of libs. I've seen Wirth pascal compiler, it's two files of a few hundreds of lines, but it's not decoupled in any way. Today most programs are larger than this because they compose lots of rules. It also brings false laziness, since you're not used to write short code, well you don't.

Re: How Chrome ate 21GB of storage

#54
post #29

Earlier quoted context omitted.

Fortunately disk space, unlike memory, is infinite.

A lot of our lapops at work (the majority, in fact) have ~240GB SSDs, so that's about 10% of their disks. Not insignificant.

I think your parent was being facetious

Re: How Chrome ate 21GB of storage

#55
post #35

Earlier quoted context omitted.

In this case, there is no need to proactively scan anymore. It was reported by users. I stressed the wrong thing before. If it can not be fixed, say so.

How do you propose third parties modifying installers without Google's knowledge or permission something Google can fix?

I think GP is just suggesting that Google has had the knowledge about this specific 3rd party issue (via this bug) for years. It can't fix all possible 3rd party installer-induced issues, but it could potentially fix this one. (Or at least notify the user.)

Re: How Chrome ate 21GB of storage

#56
post #28
post #27

> I’m happily walking away from this with an extra 21GB in my pocket! And now I ask you: is your Chrome bigger than mine? Given I don't have to rely on third party updaters, I doubt it. Let's see... $ let size=0; dpkg -L chromium | while read path; do if [ -f "$path" ]; then let size=$size+$(du -sb "$path" | awk '{print $1}'); echo $size bytes, $(($size/1024/1024)) megabytes; fi; done; 172060669 bytes, 164 megabytes…

heh, nice user@t61:~$ let size=0; dpkg -L chromium | while read path; do if [ -f "$path" ]; then let size=$size+$(du -sb "$path" | awk '{print $1}'); echo $size bytes, $(($size/1024/1024)) megabytes; fi; done; 162190110 bytes, 154 megabytes user@t61:~$ du -sh .{cache,config}/chromium 386M .cache/chromium 84M .config/chromium

I win? :P

    zod@DESKTOP MINGW64 ~/AppData/Local/Google
    $ du -sh ~/AppData/Local/Google
    2.9G    /c/Users/Zod/AppData/Local/Google
Edit: I do have 885 tabs open. (yikes! D:)

Re: How Chrome ate 21GB of storage

#58
post #18

This 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.

Chrome has gone the way of IE. Chrome is memory and energy hungry (and now storage hungry if you believe this article), and Google doesn't care. If you run Chrome on a laptop, you better plug it in.

Google “doesn't care” so much that they spent the last year working on battery life:

https://chrome.googleblog.com/2016/09/chrome-faster-and-more...

Re: How Chrome ate 21GB of storage

#59
post #28

Earlier quoted context omitted.

heh, nice user@t61:~$ let size=0; dpkg -L chromium | while read path; do if [ -f "$path" ]; then let size=$size+$(du -sb "$path" | awk '{print $1}'); echo $size bytes, $(($size/1024/1024)) megabytes; fi; done; 162190110 bytes, 154 megabytes user@t61:~$ du -sh .{cache,config}/chromium 386M .cache/chromium 84M .config/chromium

I win? :P zod@DESKTOP MINGW64 ~/AppData/Local/Google $ du -sh ~/AppData/Local/Google 2.9G /c/Users/Zod/AppData/Local/Google Edit: I do have 885 tabs open. (yikes! D:)

>885 tabs

is that intentional, or do you just never close tabs? How do you navigate tabs without losing your mind?

Re: How Chrome ate 21GB of storage

#60
post #58
post #18

Earlier quoted context omitted.

Chrome has gone the way of IE. Chrome is memory and energy hungry (and now storage hungry if you believe this article), and Google doesn't care. If you run Chrome on a laptop, you better plug it in.

Google “doesn't care” so much that they spent the last year working on battery life: https://chrome.googleblog.com/2016/09/chrome-faster-and-more...

Thanks for correcting me. I had outdated impressions.
Post reply on HN