"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 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. 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".
Now many of those same people will be spouting how great FF is because they've cut memory usage so much (and maybe how they'll venture in to the brave new world of 3-tabs-at-a-time).
End of the day, this is just how computer stuff goes - deny there's a problem, fix it, then promote how great your fix is. Just gets a bit tiresome.
Oh, and yes, I set up a bunch of strawmen up there. I love the smell of them burning in the morning.
> 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.
That's because complaints about large memory use in Firefox fall into two camps, generally:
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".
You're getting confused between Firefox and Chrome. Firefox has always been the browser of choice for the "tons of tabs" crowd, because Chrome's process-per-tab model breaks down when there's more than a few dozen open.
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.
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!"
Because every time I've seen Mozilla developers making note of memory improvements over the last few years, I run into someone claiming that every time "Firefox" and "memory usage" came up prior to whichever is current for the time, the developers steadfastly denied a problem.
It's getting a bit like the mythical proslytizing vegan; I've run into far more people bitching about however many instances of fuss-making by however many hostile vegans than I have of actual hostile vegans. (The count of the latter can be described as "basically none".)
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/2008/03/11/firefox-3-memory-usage/
Many of the Firefox 7 fixes that reduced memory usage did not have to do with fragmentation; there were a number of true memory leaks fixed, and other bugs where code was allocating more memory than it ever could need.
(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.)
They've started getting more serious about it. One of their big new JavaScript performance features, type inference, was backed out as soon as they realized it causes significantly increased memory usage -- and it won't get back in until it slims down, despite significant JS performance benefits. In the past, many features slipped in with memory problems and weren't noticed for months or years.
I smirked at the headline when I saw it and I came here to say the same thing ... Every release they promise that firefox will use less memory ... hasn't happened yet AFAIK.
There's something inherently wrong about the headline of this. How did they get to such a high usage in the first place? They sacrificed performance for features, and now going back to clean up the mess. Not elegant. This is why I'm sticking with Chrome.
Could someone help identify why Firefox saves and keeps such a ridiculous number of Cache folders in \\Application Data\...\Profiles\... They're all 0, 1, 2...and then 01, 0A, 0B. I mean, what's the point here?
Filesystem performance tends to degrade when you have tens of thousands of files in a single directory, so programs that manage thousands of files usually end up dividing them into many subdirectories. It's not just Firefox - git uses the same strategy, for example.
I'm using Firefox 5 right now, I don't feel any difference from Firefox 4.
That's exactly the point. Which version of Gmail are we on right now? 477? Does that feel different from 476? I don't know. I just get performance improvements and new features as they come out.
The problem with using that metric is that the "feel" of a program is directly related to the UI changes that the version employs. You could change absolutely nothing bug and feature wise, but do a UI redesign and the new version would feel like it was updated a whole bunch.
Clearly, they are pulling the old "major version change marketing stunt" to catch up with a perceived lag in version numbers compared to other browsers. You see, apparently people think IE 9 must be vastly superior to FF 4...
Personally, I think the time for version numbers should probably be over altogether. At this point I feel it's more productive to just tack a date string onto the thing and be done with it. For example, Firefox 2011-July is way more informative than an actual version number.
Well, even with that it won't be comparable to Chrome I'm afraid. Firefox became very heavy suring the years. And no I don't have a lot of add-ons; I have 2 addons in FF and 15 addons in Chrome and yet Chrome processes suck much less memory even if i run it for days without closing. People switching to Chrome is not just PR, really.
6 = current beta, will become release in 1-2 weeks
7 = current alpha (Aurora), will become beta when beta gets released
8 = current nightly, will become Aurora when...you get the point
So basically Firefox 6, 7 and 8 have already "come out" and you can use them if you're willing to run beta or alpha software. (In my experience, Aurora is already very stable, much more so than normal alpha software) The versions advance in a 6 weeks cycle.
I'm guessing the above has been explained about 1000 times when Firefox 5 came out soon after 4, anyway.
Firefox 7 isn't even a real release. You'll have to wait for 8. The new versioning system uses the Fibonacci sequence, so that after 8, the next "real" release will be 13, and then 21 etc. This is why you're currently stuck on 5.
I think Firefox is trying to adopt the Chrome model, which is that version numbers are for the developers only. End users shouldn't need to know which version they're running.
I'm not sure how much you're joking, but Mozilla is releasing 3 versions at a time. Release, Beta, and Aurora. Right now, Release is on version 5, Beta is 6, Aurora is 7. You can get them from http://www.mozilla.com/en-US/firefox/channel/
I don't know what everyone is complaining about, whenever I want to open a few more tabs I just purchase a couple more gigs of ram, problem solved, bunch of whiners!
[+] [-] mgkimsal|14 years ago|reply
"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 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. 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".
Now many of those same people will be spouting how great FF is because they've cut memory usage so much (and maybe how they'll venture in to the brave new world of 3-tabs-at-a-time).
End of the day, this is just how computer stuff goes - deny there's a problem, fix it, then promote how great your fix is. Just gets a bit tiresome.
Oh, and yes, I set up a bunch of strawmen up there. I love the smell of them burning in the morning.
[+] [-] jmillikin|14 years ago|reply
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.
You're getting confused between Firefox and Chrome. Firefox has always been the browser of choice for the "tons of tabs" crowd, because Chrome's process-per-tab model breaks down when there's more than a few dozen open.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.
[+] [-] onemoreact|14 years ago|reply
[+] [-] bzbarsky|14 years ago|reply
None of whom are actually active Firefox or Gecko developers...
In other words, fanboys act like fanboys. Surprise!
[+] [-] carussell|14 years ago|reply
Because every time I've seen Mozilla developers making note of memory improvements over the last few years, I run into someone claiming that every time "Firefox" and "memory usage" came up prior to whichever is current for the time, the developers steadfastly denied a problem.
It's getting a bit like the mythical proslytizing vegan; I've run into far more people bitching about however many instances of fuss-making by however many hostile vegans than I have of actual hostile vegans. (The count of the latter can be described as "basically none".)
[+] [-] sp332|14 years ago|reply
[+] [-] capnrefsmmat|14 years ago|reply
(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.)
[+] [-] hack_edu|14 years ago|reply
[+] [-] capnrefsmmat|14 years ago|reply
[+] [-] andhow|14 years ago|reply
[+] [-] trustfundbaby|14 years ago|reply
[+] [-] drieddust|14 years ago|reply
Firefox 8 is current state is performing an order of magnitude better than the current stable release.
They are definitely improving at an escalating pace ever since chrome and safari started eating into their market share.
[+] [-] marckremers|14 years ago|reply
[+] [-] oppositionradio|14 years ago|reply
[+] [-] stanleydrew|14 years ago|reply
http://www.chromium.org/user-experience/multi-profiles
[+] [-] callahad|14 years ago|reply
[+] [-] capnrefsmmat|14 years ago|reply
https://bugzilla.mozilla.org/show_bug.cgi?id=673851
[+] [-] sliverstorm|14 years ago|reply
[+] [-] starwed|14 years ago|reply
The actual statement, if you read the original source[1], is
>Firefox 7 uses less memory than Firefox 6 (and 5 and 4): often 20% to 30% less, and sometimes as much as 50% less.
[1] http://blog.mozilla.com/nnethercote/2011/08/09/firefox-7-is-...
[+] [-] u48998|14 years ago|reply
[+] [-] mbrubeck|14 years ago|reply
[+] [-] yason|14 years ago|reply
[+] [-] lurker19|14 years ago|reply
[+] [-] vegai|14 years ago|reply
Please leave this field.
[+] [-] andhow|14 years ago|reply
[+] [-] fedorabbit|14 years ago|reply
[+] [-] stanleydrew|14 years ago|reply
That's exactly the point. Which version of Gmail are we on right now? 477? Does that feel different from 476? I don't know. I just get performance improvements and new features as they come out.
[+] [-] AndyKelley|14 years ago|reply
[+] [-] Udo|14 years ago|reply
Personally, I think the time for version numbers should probably be over altogether. At this point I feel it's more productive to just tack a date string onto the thing and be done with it. For example, Firefox 2011-July is way more informative than an actual version number.
[+] [-] AlfaWolph|14 years ago|reply
[+] [-] notatoad|14 years ago|reply
[+] [-] grimen|14 years ago|reply
[+] [-] william42|14 years ago|reply
[+] [-] Maro|14 years ago|reply
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.
[+] [-] gcp|14 years ago|reply
So basically Firefox 6, 7 and 8 have already "come out" and you can use them if you're willing to run beta or alpha software. (In my experience, Aurora is already very stable, much more so than normal alpha software) The versions advance in a 6 weeks cycle.
I'm guessing the above has been explained about 1000 times when Firefox 5 came out soon after 4, anyway.
[+] [-] windsurfer|14 years ago|reply
[+] [-] andrewf|14 years ago|reply
[+] [-] scott_s|14 years ago|reply
[+] [-] sp332|14 years ago|reply
[+] [-] Thrymr9|14 years ago|reply
http://www.mozilla.com/en-US/firefox/channel/
[+] [-] fredleblanc|14 years ago|reply
[+] [-] wmf|14 years ago|reply
[+] [-] unknown|14 years ago|reply
[deleted]
[+] [-] heelhook|14 years ago|reply
[+] [-] pestaa|14 years ago|reply