In fact, on the mac, with the same number (34) of tabs, the same content, no add-ons or extensions, Firefox takes 600MB - 800MB, Safari takes around 900MB-1GB and Chrome takes around 900-1.2GB. I use these browsers every day and I have the same results every day.
I have the same tabs open now in Firefox, all 34 of them and it's only taking 740MB. You just can't beat that. It's really awesome.
(I'm not saying Firefox has memory leaks. Though it's extremely unlikely it has none, same goes for Chrome and Safari)
> Also, perhaps I'm missing something, but as far as I
> can tell Chrome is at least partially open source, no?
> http://www.chromium.org/developers/how-tos/get-the-code
>
> Why aren't people forking it to create a more privacy
> friendly version?
People citing privacy as a reason to move away from Chrome are doing so on moral rather than technical grounds. Chromium itself doesn't have anything harmful in it, so there's no point in forking. Chrome is just Chromium plus some third-party proprietary plugins (Flash, the PDF renderer).All sorts can happen between source and binary.
1. The probability of discovering something in all that binary code, especially with the intricate and non-orthogonal nature of x86/x64 assembly and odd compiler optimisations. This isn't some 80's game.
A comparison:
28500000 = Chrome binary size [1]
750000000 = Human Genome size (converted to bytes - 1BP = 2bits so 4BP per byte) [2]
So we're only 26x more complicated than Chrome and we have absolutely no fucking idea what is going on with us most of the time.2. The probability of a vulnerability being published to Google versus selling it on the private market.
The binary size may be similar but that doesn't mean the content is. Consider the two cases below to back up my assertion:
000000WE_COME_IN_PEACE000000000000000000
000000WE_COME_IN_PEACE_SHOOT_TO_KILL0000I said that the binaries could be diffed, then you responded that finding a difference is unlikely because the binary is very large. I don't understand what the absolute size of the binaries has to do with being able to compare them.
[0] https://en.wikipedia.org/wiki/Chromium_(web_browser)#Differe...
True. But also true of firefox. But you can install chromium and firefox from source and be sure that apart from your compiler nobody planted anything in your browser.
I don't think this is as terrible as you think anymore (or if it is really even an issue anymore). The MemShrink[0] project has made huge progress. See also: https://areweslimyet.com/
Yes, it has a terrible memory leak issue, but all of my computers have enough ram as to not notice.
I'm still not ready to make the switch to DuckDuckGo. I figure that if I'm going to stick with Gmail no matter what, if Google already has that information, collecting a few search queries is nothing.
Also, perhaps I'm missing something, but as far as I can tell Chrome is at least partially open source, no? http://www.chromium.org/developers/how-tos/get-the-code
Why aren't people forking it to create a more privacy friendly version?