11–20 of 102 posts
I'm using Firefox 5.0.1, I just clicked "Check for updates" and it said I'm up-to-date. Shouldn't 6 come out first? Isn't it too early to talk about 7? I think this is bad marketing from Mozilla, they're totally confusing people.
I'm using Firefox 5.0.1, I just clicked "Check for updates" and it said I'm up-to-date. Shouldn't 6 come out first? Isn't it too early to talk about 7? I think this is bad marketing from Mozilla, they're totally confusing people.
I'm reminded of MySQL. "You don't have transaction support" "Sure we do - just handle it in your code" "But I need transactions" "No you don't! That's just overarchitecting!" "No really I do" "Look how fast we are!" ... years later... "Hey look at MySQL - We have transactions! Look how great we are!" etc. I like FF. I use it. But every time there's some comment about FF memory, we usually see a bunch of people coming…
User4,27,128: "I think there might be an issue."
Fanboy37,652: "What are you talking about? This is the best thing ever!!!"
Fanboy23,418: "That easy to fix, just type everything backward while singing and it all works fine!!1!"
...
Dev15: "Fixed problem 4,129"
Fanboy37,652: "Now that that's fixed, this is the best thing ever!!1!"I'm reminded of MySQL. "You don't have transaction support" "Sure we do - just handle it in your code" "But I need transactions" "No you don't! That's just overarchitecting!" "No really I do" "Look how fast we are!" ... years later... "Hey look at MySQL - We have transactions! Look how great we are!" etc. I like FF. I use it. But every time there's some comment about FF memory, we usually see a bunch of people coming…
You often see the same pattern with OS. User4,27,128: "I think there might be an issue." Fanboy37,652: "What are you talking about? This is the best thing ever!!!" Fanboy23,418: "That easy to fix, just type everything backward while singing and it all works fine!!1!" ... Dev15: "Fixed problem 4,129" Fanboy37,652: "Now that that's fixed, this is the best thing ever!!1!"
I'm reminded of MySQL. "You don't have transaction support" "Sure we do - just handle it in your code" "But I need transactions" "No you don't! That's just overarchitecting!" "No really I do" "Look how fast we are!" ... years later... "Hey look at MySQL - We have transactions! Look how great we are!" etc. I like FF. I use it. But every time there's some comment about FF memory, we usually see a bunch of people coming…
> I like FF. I use it. But every time there's some comment
> about FF memory, we usually see a bunch of people coming
> out saying they never see FF memory issues, the OP must be
> doing something wrong or have a bad system, they use their
> computer non-stop for 4 years without ever even seeing FF
> slow down, etc.
1. "I left Firefox on overnight with three tabs open, and now it's using 3.1 GiB of memory. This browser is terrible! Yes, I do have dozens of low-quality extensions installed, so?"
2. "I started Firefox, and already it's using over 300 MiB! That's insane! Why would a web browser ever use that much? I'm switching to Chrome, it only uses 100 MiB. What do you mean, 'multiple processes'?"
There may in fact be genuine issues buried somewhere in the discussion, but they're hard to discern against the general background noise.
> Then endless discussion about "how can you even function
> having more than 2 tabs open? I always close all mine
> because of some cognition study from 1974 which I read in
> my one open tab, then closed it".
For example, I have just over 70 tabs open right now, Firefox has been running for about a month, and it's at 1.1 GiB resident memory. Chrome becomes very unhappy under such circumstances (since it uses about ~100 MiB per tab), so I'm careful to only open a few tabs at a time.
I'm using Firefox 5.0.1, I just clicked "Check for updates" and it said I'm up-to-date. Shouldn't 6 come out first? Isn't it too early to talk about 7? I think this is bad marketing from Mozilla, they're totally confusing people.
It's not that Firefox is actually using that much memory. It's not even that it has a memory leak in the usual sense of a broken garbage collector or something. It all down to memory fragmentation. You can see illustrations of browser memory fragmentation here: http://blog.pavlov.net/2007/11/10/memory-fragmentation/ Firefox switched to jemalloc in 2008, which cut memory usage to less than half. http://blog.pavlov.net…
(For example, I think there was a bug where the find-as-you-type bar could keep the page in memory forever if it wasn't dismissed.)