News for hackers. Stuff that matters.
Re:Everybody Hates Firefox Updates by smacktoward on Friday July 06, 2012 @05:19PM (#4209699)
I think the takeaway from this should be slightly different than the one the author found: don't fight users' expectations of what your product is.

When Chrome came out, it was a new product; users had no expectations of "what Chrome is." So Google could do with it essentially whatever they wanted.

Firefox was in a completely different position. When Mozilla moved Firefox to rapid release, the product branded "Firefox" had been in users' hands for seven years -- nine if you count pre-1.0 versions. Over that time, users' expectations of what a product branded "Firefox" was settled into a particular place.

Rapid release was painful because it broke those expectations. Suddenly Firefox didn't behave like people expected a product labeled "Firefox" to behave anymore. It's like opening a bottle labeled "Coke" and having orange juice pour out. "But orange juice is better for you!" Yeah, but that's still not what I expect to get when I open a Coke bottle.

There's a simple way Mozilla could have avoided this: just call the rapid-release product something else. Create a new brand, and put it on a version of the browser that receives updates every six weeks. Call it Fastfox or Frequentfox or really anything other than Firefox. Then encourage users to start moving from Firefox to the new hotness. Make the new product compatible with Firefox extensions, but don't do the version-number compatibility check that Firefox does, so users aren't constantly being prompted to update working addons.

(Yes, both products are the same code under the hood. That doesn't matter. The important thing is that you communicate to users that this is a thing that is something other than Firefox, which resets their expectations.)

Eventually you'd have most users on the new product, since that's where the cool new features that get users excited would be showing up. Curmudgeons and enterprises would stay with boring old Firefox, but that's OK, because you make "Firefox" just a periodic snapshot of Frequentfox development. "Firefox" becomes a legacy brand, maintained for those who care about it. But the new brand is clearly established as the new hotness.

This lets you move your users without violating their expectations. They expect the new product to behave differently, because it's a new product. It's got a different name and everything!

Violent changes in direction for an established product, on the other hand, always tick off users, because they do violence to those users' expectations of what that product is.

It's better to send your well-loved legacy brand gracefully off into the sunset, in other words, than to try and shock new life into it with electric paddles.

Re:Everybody Hates Firefox Updates by samspot on Friday July 06, 2012 @07:21PM (#4210059)
You are of course entitled to your opinion but I must disagree. Users don't care what it iss called, they care about being annoyed. Firefox was always nagging you about updates while chrome silently updated in the background. And I personally have never had a chrome update do anything that I noticed immediately (like breaking my addons.)

I disagree about expectations too. Users have a great deal of built in expectations for chrome after having dealt with other browsers for years.

If firefox and chrome switched their update systems, the story we would be hearing would be "I tried chrome and i hated it.", and they probably wouldn't even bother to tell us why (the nagging update system.)

Re:Everybody Hates Firefox Updates by brigade on Friday July 06, 2012 @05:26PM (#4209737)
So annoying your users with constant updates, reboots, and breaking functionality is okay as long as you do it from the start? And the way to get people to accept you adding such annoyance to your product is to rebrand it?

Okay then.

Re:Everybody Hates Firefox Updates by smacktoward on Friday July 06, 2012 @05:32PM (#4209757)
No, but if you must move to a more rapid update schedule (as the Firefox developers clearly felt they did to stay competitive with Chrome, since users were screaming against rapid release from practically the moment the plan was announced and they went ahead with it anyway), moving the rapid updates into a new product is less disruptive than shoehorning them into your existing one.
Re:Everybody Hates Firefox Updates by lovskogen on Saturday July 07, 2012 @04:39AM (#4211138)
Rapid updates doesn't need to be disruptive, look at Chrome. I don't think Firefox users will miss the Update Dialogue if they removed it, and did silent updates as Chrome. Fragmenting into two apps, and keeping an app with slower update cycle and a crappy update experience, seems bizarre.
Re:Everybody Hates Firefox Updates by dredmorbius on Friday July 06, 2012 @05:34PM (#4209768)
Very well said.

Previously, when I went to a new browser experience, I generally went to a new browser.

There was Mosaic. Then Netscape. Then Galeon. Then Konqueror. Then Mozilla. Then Firefox.

Galeon was probably the most jarring of the bunch. It started as a highly power-user friendly advanced (for the time) browser. Then the GNOME project "adopted" it as its default browser ... and instilled it with "simple user" disease. Many features were ripped out, and much of the userbase left in disgust (there are a few postings by Jon Corbet and other at LWN.net I recall). Eventually it was replaced by Epiphany, a pale shadow of the original.

Life would have been better if the rebranding had happened first.

And we'll note that Mozilla has already gone this route several times: Netscape -> Mozilla -> Phoenix -> Firefox. They should have taken this as a new fork as well.

Re:Everybody Hates Firefox Updates by fallous on Friday July 06, 2012 @11:38PM (#4210644)
Mozilla kept me from Firefox for years. The idiotic "view source" that actually re-fetched the page made it utterly worthless for development and when the bugs were filed, they were promptly ignored.

That said, with the except of one FF push on OSX that broke Netflix for a few days I've been pleased with the changes. Safari's constant memory leaks drove me nuts, FF leaking memory wasn't as bad but certainly annoyed. They've solved that problem for my usage and having suffered with Chrome "dev tools" I continue to use FF and Firebug for front-end work when need be.

Re:Everybody Hates Firefox Updates by bgruber on Saturday July 07, 2012 @01:09AM (#4210783)
oh galeon, how i miss thee, particularly your sane address bar tab-completion. anyone know if there's anything comparable as a chrome extension or firefox addon?
Re:Everybody Hates Firefox Updates by dredmorbius on Saturday July 07, 2012 @08:51PM (#4213190)
What was the address-bar tab-completion functionality?

Have you tried Vimperator for Firefox?

Modal, action happens on a status line at the bottom of the screen (allowing you to minimize navigation elements -- no navigation, menu, or toolbars). To open a new tab, type "t <pattern><tab>", where "pattern" is either part of a URL or the title of a page or bookmark. To open Hacker News, for example, I generally type "t hack<tab>". If there are multiple matches, they appear as a list of items you can tab through (or which shrinks as you type additional characters for greater specificity). I like it.

Chrome's navigation is similar, but not quite as slick.

Re:Everybody Hates Firefox Updates by morsch on Friday July 06, 2012 @10:47PM (#4210546)
I'm not sure most users would move to the new product. Most people stick to the software they use. That might be because they don't want to learn a different interface. But I think, fundamentally, many people don't even want to deal with the existence of alternatives, they're blissfully ignorant of choice and of weighing up- and downsides[1]). I'm the same way with laundry detergent. That's a fickle kind of loyalty, though.

So, if that's true and people stuck with Firefox, you'd have to maintain Firefox between the snapshot releases of Frequentfox. You'd have to push an update at least every time you fix a security issue, which can be pretty often. So you'd still need to figure out a good user experience for dealing with frequent updates. Fortunately, that's a solved problem, and the user doesn't even need to notice you've updated their software.

Of course as you add features and modify/improve the user interface in Frequentfox, your Firefox snapshots will be different enough that you'd still end up alienating users, so you can't go crazy developing Frequentfox, either.

I'm voting for frequent push updates, transparent if they don't change anything significant, and with a gentle introduction to the changes if they do. Big changes should be rare, maybe explain the motivation behind them to the user, and ideally make them option. Despite all the rage, I think the user interface changes from Firefox 3 to trunk weren't all that jarring; significant tweaks more than fundamental reworkings of the UI, the awesome bar is a great example.

[1] Edit: I think this is what you call a "second-order decision", a term I just learned, e.g. http://thinking-marketing.blogspot.de/2009/11/second-order-d...

Re:Everybody Hates Firefox Updates by jono_x on Friday July 06, 2012 @07:56PM (#4210159)
Hi Smacktoward, I'm the author of the post and I agree with everything you said here.

How to reach out to new users while keeping your existing users happy is one of the oldest and biggest problems in software development. There's no perfect solution, but I like the suggestion of creating a new product name for the new thing. That can sometimes get you into trouble too, as you end up competing with yourself, Microsoft-style, or get users who are confused about which version they should use. But it might be the least bad option.

Re:Everybody Hates Firefox Updates by lovskogen on Saturday July 07, 2012 @04:32AM (#4211129)
I disagree, and I think you're set on the auto-update in Chrome and Firefox on being equal – they're not. Average Joe doesn't care about a update that brings support for a new css selector – but he cares if that update smacks him in the face. Firefox smacks him in the face, Chrome doesn't.
Re:Everybody Hates Firefox Updates by azakai on Friday July 06, 2012 @08:06PM (#4210193)
> I think the takeaway from this should be slightly different than the one the author found: don't fight users' expectations of what your product is.

That's a fair point, but also true is "don't let your product stagnate by keeping it familiar and unchanging". People get bored with similarity and want new shiny things.

There is something to be said for too much change, and something to be said for too much sameness.

Re:Everybody Hates Firefox Updates by jono_x on Friday July 06, 2012 @09:53PM (#4210441)
> That's a fair point, but also true is "don't let your product stagnate by keeping it familiar and unchanging". People get bored with similarity and want new shiny things.

I disagree. Users want something new if their current software isn't meeting their needs for whatever reason. But if it is meeting their needs and they know how to use it, then keeping that software the same isn't "stagnation", it's stability.

Whenever I hear users ask for change it's because there's a feature they wish they had or a bug that's annoying them. I've never heard anybody ask for change just for the sake of change, or complain that software was boring because it didn't change.

For games I guess it might make sense to keep changing things up just to keep them fresh, but for productivity software I think "boring, predictable, and functional" is the ideal state. Productivity software isn't supposed to be entertaining, it's supposed to be useful.

Re:Everybody Hates Firefox Updates by azakai on Saturday July 07, 2012 @12:13PM (#4211983)
> Users want something new if their current software isn't meeting their needs for whatever reason.

What if their need is for something new and shiny?

Have you never heard people say they tried Chrome because it was new and shiny (even the word implies shininess)? Or how about how people want to buy the latest iPad or iPhone, it isn't because the old one isn't "meeting their needs" in some boring sense. They want something new and different.

> Whenever I hear users ask for change it's because there's a feature they wish they had or a bug that's annoying them

That is a very simplistic view of users. Users are human beings - they want conflicting things, both for things to work and be predictable, and for things to be new and interesting.

The right tradeoff is the hard part, not absolute black-and-white principles of "users never want change" or "users always want something new and shiny".

Re:Everybody Hates Firefox Updates by maratd on Friday July 06, 2012 @05:45PM (#4209806)
They kind of took a stab at solving this. Firefox ESR. It's what Firefox used to be.
Re:Everybody Hates Firefox Updates by Silhouette on Friday July 06, 2012 @06:05PM (#4209863)
The thing is, even the ESR is only supported for about a year before being completely cut off in favour of a new ESR that has only been available for about 6-12 weeks at that point.

There are some large businesses out there who run the same software foundation for a decade or more, not least because just evaluating a new version of something critical like an operating system or web browser can be a huge exercise if you're running hundreds of in-house tools on top of them.

While I think it's unrealistic to expect an OSS browser to provide ongoing support for that long, if Mozilla want their product to be taken seriously by enterprise customers then I suspect they're going to need a lot more than a year of security fixes and a lot more than 6-12 weeks of overlap when they want to force an upgrade. It would be interesting to know whether in reality they have gained much from offering the first ESR (which is already coming to end-of-life) in terms of acceptance of the rapid release schedule in larger organisations. Maybe there is a certain size of organisation that is flexible enough to take advantage of a yearly update but can't take the overheads of stuff breaking every six weeks.

Re:Everybody Hates Firefox Updates by azakai on Friday July 06, 2012 @11:53PM (#4210674)
> The thing is, even the ESR is only supported for about a year before being completely cut off in favour of a new ESR that has only been available for about 6-12 weeks at that point. There are some large businesses out there who run the same software foundation for a decade or more.

For software like that, a web browser is not the right platform. Web browsers view a shared space which constantly changes and gets updated with new APIs and deprecated APIs and so forth.

If you want decade-long stability, use a platform that is tightly controlled and gives guarantees of backwards compatibility, for example Java or .NET.

Re:Everybody Hates Firefox Updates by Silhouette on Saturday July 07, 2012 @07:13AM (#4211380)
For software like that, a web browser is not the right platform. Web browsers view a shared space which constantly changes and gets updated with new APIs and deprecated APIs and so forth.

You seem to be confusing the Internet with corporate intranets. Browsers installed in these kinds of organisations, and the tools they want to use long-term, tend to be based around the latter. Having stability is far more important than being able to use HTML5 local storage and add drop shadows to your titles in CSS. There is a reason that, despite the endless moaning of web developers, many places are still running IE6.

If you want decade-long stability, use a platform that is tightly controlled and gives guarantees of backwards compatibility

They are. Unchanged is about as controlled and backward compatible as you can get!

Anyone who wants to get a replacement browser into these environments for the long term needs to understand that. Anyone who wants to make cloud-based solutions that seek to displace well-established in-house tools needs to understand that, too. It sucks if you want to use the shiny new possibilities of bleeding edge web technology, but the grown-ups aren't interested in an anatomical measuring contest between browser makers about who can be first to ship the next non-standardised, subject-to-change-at-any-time, bug-ridden-anyway feature.

I think Microsoft does understand this, and that's why they are still dominant in large organisations despite appearing to be behind the curve. I think Google have figured it out as well, but when they stopped supporting IE6 in their web apps, it wasn't because they had successfully forced everyone to upgrade, it's because they realised that they never would.

Re:Everybody Hates Firefox Updates by azakai on Saturday July 07, 2012 @12:18PM (#4211996)
The point is that a browser that can view the modern web is different than one that can run a 10-year old intranet app. These are very different things. I agree with you that corporations sometimes need both.

Since there are open source browsers, you can just save a very old version of them for intranet apps, if you must. But you can't expect a modern browser to still run your old intranet apps, you will need both a legacy browser and a modern one.

The ESR fits somewhere in the middle. It won't run 10 year-old apps, but it will update very slowly so your IT department does not need to constantly verify it (only once a year). Again, for 10-year-old apps, that won't work - you just need to install a 10-year old browser. If you just run it on intranet apps, security isn't a concern so that's fine.

Re:Everybody Hates Firefox Updates by yuhong on Saturday July 07, 2012 @05:08PM (#4212733)
Indeed, the parent did say that:

>While I think it's unrealistic to expect an OSS browser to provide ongoing support for that long

Re:Everybody Hates Firefox Updates by smashing on Saturday July 07, 2012 @01:29AM (#4210821)
"All software sucks. Users would be a lot happier if they had to use a lot less of it."

According the the author, Chrome isn't the solution.

Re:Everybody Hates Firefox Updates by earl on Friday July 06, 2012 @07:06PM (#4210023)
The other thing is that Chrome updates work. They've only broken something once in I think 3 years of daily use at this point (some update unchecked "warn before quitting"). They also don't generally create popups and the update process itself is literally invisible.

Firefox on the other hand... sigh. I really liked that browser, but the updates, and the broken plugins, and the shit memory management, and the developers' heads up their shitty asses denying their shit memory management, and did I mention the enormous memory usage on OSX? Chrome essentially has the same uptime as my laptop, ie months. Firefox required daily restarts with the same browsing patterns. Plus they regularly corrupt the backing file that holds the sites you had open in your browser, so before restarting the browser to get ram back, it's a best practice to copy the location of each and every open tab to a text file.

We got my gf's laptop 8 gigs of ram to accomodate ff and I'm working on talking her into chrome. A browser written by people who know how to use free(3). Plus the updates don't hork random stuff. Plus on the rare occasions I've restarted the browser it has never broken the backing store holding the open tabs.

Re:Everybody Hates Firefox Updates by dangoor on Friday July 06, 2012 @07:55PM (#4210154)
Actually, Firefox developers care a good deal about memory management. More than Add-on authors unfortunately.

We've had a project called MemShrink running for about a year and it has been making steady progress. and that progress has been shipping to users.

The current Aurora channel release even has a fix for most add-on bad behavior.

Firefox actually stacks up really well in memory usage (even in third party tests).

(I work for Mozilla but was not involved in MemShrink. Also, I wrote this on my phone, so I hope there are no embarrassing misspellings. )

Re:Everybody Hates Firefox Updates by thaumasiotes on Friday July 06, 2012 @09:01PM (#4210333)
I quit firefox purely over its tendency to leak my entire RAM and force restarts. I was told at the time, and do believe, that the memory leaking was an addon problem. However... firefox was sold on the idea of addons. When your two main messages are "we're the most convenient browser; just look at all our awesome addons!" and "you can't use the addons, or your computer will implode", you've got a serious problem.
Re:Everybody Hates Firefox Updates by forrestthewoods on Friday July 06, 2012 @10:01PM (#4210465)
I quit using Firefox due to absolutely horrific memory management and I never used a single add-on ever. It was extremely frustrating because every time I went to a forum seeking help the first and only thing people would do is blame add-ons.

It was so bad that I had to close firefox when I wanted to do anything else. If I played a full screen game it would work great for about half an hour the suddenly it'd chug along at 10fps. Without fail the issue was Firefox deciding to consume 90% CPU. And again this is without installing a single add-on ever.

It may be better today. I don't know. I don't care. I switched to Chrome and haven't looked back since.

Re:Everybody Hates Firefox Updates by karlshea on Saturday July 07, 2012 @01:18PM (#4212156)
This is exactly right. The party line was "it's the addons" forever, anytime you brought up Firefox taking up 900MB of RAM after being open for 3 days. Even with no addons. I was so glad to switch to Chrome when it came out because of that.

And then years later they have the "MemShrink project". Which basically was admitting that they were spouting bullshit about it being addons for years.

Re:Everybody Hates Firefox Updates by botj on Saturday July 07, 2012 @12:27AM (#4210719)
Haters-be hate'n. And how exactly does the one process per tab of chrome address memory issues? Chrome is complete garbage for me after 30ish tabs. Talk about unresponsive...
Re:Everybody Hates Firefox Updates by wanderr on Saturday July 07, 2012 @05:00AM (#4211173)
The great thing about this model is that closing the tabs kills the processes and therefore frees up memory. Last time I used FFx extensively (6 months-1year ago) I could not say the same thing, even after they announced having a pretty major fix for leaks.
Re:Everybody Hates Firefox Updates by dredmorbius on Saturday July 07, 2012 @06:59PM (#4212976)
In Chrome you can kill and/or restart tabs without losing your entire session.

State recovery is quite good for the most part, even if memory use is somewhat pants.

Re:Everybody Hates Firefox Updates by lobo_tuerto on Saturday July 07, 2012 @12:19PM (#4211999)
Chrome user in Ubuntu, 30ish tabs don't make unresponsive my browser here.
Re:Everybody Hates Firefox Updates by ingenium on Sunday July 08, 2012 @05:02PM (#4215701)
I quit Firefox as soon as Chromium for Linux was available. My problem with Firefox wasn't so much the memory leaks (though those were annoying), but rather that it was SLOW. Opening new tabs caused the whole UI to grind to a halt while they rendered....and this wasn't on a slow computer. I've heard that FF has finally been multithreaded, but I haven't really tested it.

This isn't to say Chrome doesn't have its own memory or performance problems. GMail for example will eat up to 1GB of memory eventually before I notice I'm low. I have to actually close the tab (reloading doesn't fix it) and re-open it. It's "only" using 500MB right now...

Re:Everybody Hates Firefox Updates by nnethercote on Friday July 06, 2012 @11:55PM (#4210677)
Please try FF15 when it comes out on August 28. It has a fix that prevents 90%+ of leaks from add-ons. See http://blog.mozilla.org/nnethercote/2012/05/07/update-on-lea... for some details (and note that all the follow-on problems mentioned in that post have now been fixed).
Re:Everybody Hates Firefox Updates by cpunks on Saturday July 07, 2012 @03:17PM (#4212432)
The problem is not add-ons. Let me repeat that -- THE PROBLEM IS NOT ADD-ONS. I left Firefox about a year ago, once Chrome was good enough, because my plain-vanilla Firefox, with all the tweaks to limit memory usage enabled, would still leak memory until it crashed (my laptop has 1.5GB RAM and Ubuntu; it also had a few GB of swap). Closing tabs did not help either. The only response from Mozilla was 'add-ons.' Chrome does just fine with 30+ tabs open on the same machine.

Any organization that can live in denial for years and years about the core issue with their product is going to die. Mozilla is tightly connected to the web developer community, but has a complete disconnect from the problems facing its actual users. When Firefox shipped, it was a great, light-weight alternative to Mozilla. From my point of view as a user, I haven't seen any substantial improvements since 1.0 shipped in 2004 -- spell check is nice, and given how often it crashes, restoring tabs when the browser is opened is nice -- but that's all. Otherwise, if not for security issues and web site compatibility issues, I'd be on Firefox 1.0 (which worked fine on sub-GHz machines).

Aside from that, virtually all development effort has been aimed at making a better IDE for web developers. I guess that benefits me since, ultimately, I can visit nicer web sites in Chrome.

Re:Everybody Hates Firefox Updates by jtheory on Sunday July 08, 2012 @05:19PM (#4215758)
There are a lot of users here complaining about Firefox memory usage who don't use it anymore.

Which is expected, because why would you stay if you were really bothered?

Comments from an active user, though... I've stuck with Firefox out of habit probably more than anything else, but now most of the things people (including me) were complaining about are already gone -- as of the last update, Firefox with -- sheesh, I guess I have about 100 tabs in 2 windows -- takes up under 500MB after using it all day, and in the morning it starts in a few seconds (they don't force-reload all your open tabs on startup anymore, just the active ones and I think text from the others is cached locally).

Chrome becomes unusable if I try to use it like a to-do list like this, for UI as well as memory reasons; not that I could say easily how much memory Chrome is using at the moment, with 20 tabs; the separate processes defeats seeing that easily, alas (there must a simple way to check, but I haven't tried).

It's quite stable, and even when it was still crashier (last year?) it's been years since I've actually lost my tabs after a crash; they've always been auto-recovered (and it has that nice prompt to let me close the ones I think may be causing trouble before relaunching).

Given different usage patterns, etc., I have no idea if people trying the actual, current FF will want to go back -- but for anyone who left more than a few months ago (especially if you left due to memory footprint) I'd suggest trying it again sometime.

[And I like the more frequent releases, personally -- I always hated the slow release cycle, and feel like they're starting to get into the swing of it now -- but I obviously don't speak for the crowd on this one...]

Re:Everybody Hates Firefox Updates by yuhong on Wednesday July 11, 2012 @11:44PM (#4232891)
A year ago at what release?
Re:Everybody Hates Firefox Updates by cpunks on Friday July 13, 2012 @08:26AM (#4239495)
Don't know. I grab from official web site, so latest as of a year ago.
Re:Everybody Hates Firefox Updates by yuhong on Friday July 13, 2012 @01:11PM (#4240694)
AFAIK Mozilla MemShrink was started around that time: http://blog.mozilla.org/nnethercote/2011/06/22/memshrink-pro...
Re:Everybody Hates Firefox Updates by ehsanu1 on Friday July 06, 2012 @11:03PM (#4210579)
So they actually had a great fix recently where they managed to largely stop addons from causing memory leaks: http://blog.mozilla.org/nnethercote/category/memshrink/
Re:Everybody Hates Firefox Updates by derefr on Friday July 06, 2012 @09:10PM (#4210351)
I don't see how that's a serious problem. An add-on ecosystem can be explained literally as "we let third parties who aren't as skilled as browser-developers develop (optional) parts of our browser." That has both obvious advantages (there are way more developers passing that lower bar, serving many more needs) and obvious drawbacks (a lot of them... can't code very well.)
Re:Everybody Hates Firefox Updates by devicenull on Saturday July 07, 2012 @06:37PM (#4212943)
I had to stop using it at work.. I'd have to restart every 2-3 hours or performance became unbearably slow. The only other "solution" was to remove all my addons, and without the addons there was really no reason to continue using firefox (Firebug was supposedly the main issue, but without firebug I can't do any work)
Re:Everybody Hates Firefox Updates by nexxer on Tuesday July 10, 2012 @01:37PM (#4225041)
I never got used to Chrome's Developer Tools. Firebug and a properly working Scrollbar Anywhere / Grab-n-drag (lets you right click anywhere and drag up and down to scroll anywhere in the page) are the only extensions keeping me on Firefox.

The equivalents on Chrome are simply not good enough. I don't know if this is an issue with all Chrome extensions, but Wet Banana / Scrollbar Anywhere on it seem to be running in a low priority and thus have sub-par performance. Scrolling is choppy and doesn't always even initiate, depending on where on the page I right-clicked.

Re:Everybody Hates Firefox Updates by smsm42 on Friday July 06, 2012 @10:14PM (#4210482)
Progress is nice, but unfortunately as a user I don't care too much about progress if the bottom line is the same. Sorry to sound disdainful about your efforts, and I know how hard it is, and I have greatest respect for the efforts of Firefox developers, but the bottom line is - it is (was, last time I checked) still leaking like Eratosthenes' sieve, and still becomes unusable after mere days of work. And even admiration for the product and all the history of it can only hold the user for so long when viable alternative is out there.
Re:Everybody Hates Firefox Updates by thristian on Friday July 06, 2012 @10:47PM (#4210545)
To counter your anecdote with another, different anecdote with more numbers in it, back in the days of Firefox 4 and subsequent versions, it would not be unusual for my Firefox to hit 500MB to 1GB of RAM usage after a day of browsing. Right now, my Firefox 15 has been running for a day, and about:memory says the total is 363.26MB. Firefox has slimmed down a lot in the past year.
Re:Everybody Hates Firefox Updates by smsm42 on Friday July 06, 2012 @11:06PM (#4210586)
Well, maybe I'll give it a try soon again. I did about a year ago and was re-disappointed.
Re:Everybody Hates Firefox Updates by nnethercote on Friday July 06, 2012 @11:58PM (#4210681)
The first big post-FF4 improvements were in FF7, which was released in September last year. See http://blog.mozilla.org/nnethercote/2011/08/09/firefox-7-is-... for some details.

And things have improved quite a bit more since FF7.

Re:Everybody Hates Firefox Updates by yuhong on Wednesday July 11, 2012 @11:46PM (#4232896)
I personally noticed this too.
Re:Everybody Hates Firefox Updates by streptomycin on Friday July 06, 2012 @10:40PM (#4210536)
> still leaking like Eratosthenes' sieve

It leaks a lot when it's using a tiny amount of memory, and it leaks hardly at all when it's using a large amount of memory?

Re:Everybody Hates Firefox Updates by smsm42 on Friday July 06, 2012 @11:05PM (#4210582)
No, it leaks endlessly without any theoretical bounds and there's no amount of memory that it's leaking won't exceed given enough time.
Re:Everybody Hates Firefox Updates by streptomycin on Saturday July 07, 2012 @09:36AM (#4211596)
So you're saying that it's more like a normal sieve than Eratosthenes' sieve?
Re:Everybody Hates Firefox Updates by pixelbath on Sunday July 08, 2012 @03:13AM (#4213963)
Apparently it only leaks into address locations that are prime, and setting all others to null.
Re:Everybody Hates Firefox Updates by dredmorbius on Saturday July 07, 2012 @07:07PM (#4212997)
Sorry, but not that I've seen in any version of Firefox I'm using. Presently ~15 at work (Ubuntu 11.10) and Iceweasel 10 at home. On an 8 GB system, I'm constantly reviewing my browser memory usage and killing/restarting browser sessions on account of memory usage. iceweasel VIRT presently 2163MB.

Sorry, but that's totally nuts.

Mozilla have been claiming "we've solved the memory leak problem" about as long as Microsoft have been claiming "we've solved the virus/security problem", or so it seems. With about the same level of credibility.

Re:Everybody Hates Firefox Updates by jtheory on Sunday July 08, 2012 @05:26PM (#4215781)
I wonder if there are large differences based on usage patterns.

I just finished entering a comment above suggesting people should give it another try; I have 100 or so tabs open and 500MB footprint after using it all day, with version 13 (I just stick with the release update channel) in win7.

In my experience they've very clearly fixed whatever the main memory issue was that affected my experience -- but not yours. Though -- the windows versions may get a bit more testing....

Re:Everybody Hates Firefox Updates by dredmorbius on Monday July 09, 2012 @11:46AM (#4218691)
How are you measuring usage? On what platform?

I'm running Firefox 15 / Iceweasel 10 on Ubuntu and Debian respectively, watching VIRT (total virtual memory size). Currently sitting at 2.3 GB, FML.

Re:Everybody Hates Firefox Updates by luser001 on Tuesday July 10, 2012 @04:47PM (#4226096)
Hmm, I'm no expert. But AFAIK open memory mapped files are counted towards a process's virtual memory (as displayed by utils like 'top' and 'ps). Dunno if FF uses memory mapped files extensively.

There's a utility called 'pmap' that you can use to display the memory mapped files and subtract it from the total etc.

Finding out how much memory a program is using is surprisingly tricky to compute. Good luck.

Re:Everybody Hates Firefox Updates by tedunangst on Friday July 06, 2012 @10:04PM (#4210470)
I would like to believe you, but since every Firefox release is faster than ever and uses less memory, if that were really true Firefox would run on an Atari and be so fast it would literally travel into the future to fetch pages. But that's not the case.
Re:Everybody Hates Firefox Updates by dbaupp on Friday July 06, 2012 @10:58PM (#4210569)
Your assertion is entirely false. Just because something keeps getting larger/faster/smaller doesn't mean it will eventually be arbitrarily large/fast/small. e.g. the sequence 1, 1 + 1/2, 1 + 1/2 + 1/4, 1 + 1/2 + 1/4 + 1/8,... keeps getting bigger and bigger, but it never goes past 2.

(Futhermore, in my personal experience, Firefox has been using less and less memory.)

Re:Everybody Hates Firefox Updates by tedunangst on Saturday July 07, 2012 @04:03PM (#4212561)
Your sequence is growing, albeit at a decreasing rate, so I'm not sure it's a good fit for memory usage. Unless you meant to say the rate at which Firefox is bloating is slowing. I could believe that. But Firefox is claiming memory usage is following a sequence more like 1/2, 1/3, 1/4, ... Which should approach zero.

If you meant your sequence to represent performance, maybe that's what's happening, but then I think they should stop saying "now 1/1024 faster than before" as if it's a reason to upgrade.

Re:Everybody Hates Firefox Updates by dbaupp on Monday July 09, 2012 @05:19AM (#4217323)
That sequence was merely an example of something that is monotonic and bounded, it wasn't chosen to be a model for memory usage or performance or anything like that.

Also, I don't see Mozilla claiming memory usage follows a curve like 1/x. In fact, I don't seem them claiming anything about long term memory usage other than "it's decreasing", which is true, and can be true without implying that the memory usage will eventually be 0.

(Btw, I don't think Mozilla have ever said something as frivolous as "1/1024 faster".)

Re:Everybody Hates Firefox Updates by tedunangst on Monday July 09, 2012 @02:14PM (#4219522)
What I meant by 1/1024 is either the changes are noticeable or not. If they aren't, don't talk about them.
Re:Everybody Hates Firefox Updates by ascendant on Friday July 06, 2012 @08:25PM (#4210243)
Sadly though now users have had years of poor memory management burned into their memories. Regardless of if it was FF or the addons, it's associated with FF now and will take time to shed.
Re:Everybody Hates Firefox Updates by aviraldg on Friday July 06, 2012 @08:28PM (#4210254)
Okay, this might sound funny, but Firefox is actually faster than Chrome on my crappy netbook which has about a gig of RAM. Plus, it can handle more tabs (200+, don't ask) without bringing the thing to a screeching halt.

I'm pretty sure you're talking about an earlier version of Firefox -- I agree, there were problems there, but things have gotten much better with the latest versions. I run Firefox Aurora (which is kinda equivalent to Chrome's dev channel) and I haven't seen anything breaking yet.

I've also used Chrome [dev] for a while and while it was pretty good, it also decided to declare that "my user profile was corrupt" after every few days. Not fun. Plus, it could hardly handle 50+ tabs, but I guess that is due to the way the Chromium sandbox and tab threading model works (and the Atom processor in my netbook.)

tl;dr: I run Firefox Aurora (with 200+ tabs) on a netbook with 1 gig of RAM. Where's that memory problem you were talking about?

Re:Everybody Hates Firefox Updates by pdw on Sunday July 08, 2012 @03:52AM (#4214030)
That matches my experience. Chrome can (according to its internal task manager) easily use over 100MB per tab which adds up quickly. Firefox is much more frugal. And for me Chrome's memory leaks are worse then Firefox's ever were.
Re:Everybody Hates Firefox Updates by slurgfest on Friday July 06, 2012 @07:36PM (#4210097)
Memory management was terrible for ages and ages before the updates. I don't think the updates ever broke memory management.

if you don't use addons, the memory management in Firefox is pretty good - actually measure it competitively against Chrome sometime

Re:Everybody Hates Firefox Updates by dbaupp on Friday July 06, 2012 @11:03PM (#4210580)
I find it is much better than Chrome.

If I have more than a handful of tabs open in Chrome then Chrome starts using significantly more than a GB of RAM (in total, across all the separate Chrome processes), while I've currently got a Firefox session that has been open for more than a week, with 30+ tabs, and is using just under 1 GB.

Re:Everybody Hates Firefox Updates by kalleboo on Saturday July 07, 2012 @06:46AM (#4211342)
How are you adding together the Chrome processes? Often when you look at the memory usage of a process, it'll incude all the shared libraries it's using. So if you add together multiple processes, you'll multiply the memory used by that shared library by the number of processes you're adding, even though that memory is, well, shared.
Re:Everybody Hates Firefox Updates by dbaupp on Saturday July 07, 2012 @08:27AM (#4211463)
Oh. Hadn't realised that, thanks for the info. :) (I am doing it naively, just from the output of ps, so your point applies. Is there an Chrome equivalent for Firefox's about:memory?)

Even so, with many tabs open, my computer hits swap far more under Chrome than Firefox.

Edit: Ah, yep, answered my own question: about:memory works in Chrome too. Using that, I've got Chrome at 360 MB with 5 tabs and 2 extensions, while Firefox is at 900 with 30+ loaded tabs and ~20 extensions.

Re:Everybody Hates Firefox Updates by TwoBit on Saturday July 07, 2012 @06:05AM (#4211265)
huh? Under heavy usage FireFox is better at memory management than Chrome. The memory problems were, what, three years ago or more?
Re:Everybody Hates Firefox Updates by noselasd on Saturday July 07, 2012 @09:27AM (#4211572)
That may be, but you can get rid of the memory that chrome uses. Just close the tab, which releases that memory - since one tab is run as a separate process which then exits and releases all memory.

With Firefox, you have to restart Firefox. All tabs run in the same process, and memory is generally not released back to the OS when someone just calls free() or delete.

Re:Everybody Hates Firefox Updates by recoiledsnake on Friday July 06, 2012 @06:09PM (#4209874)
The problem with your suggestion is that they will have to maintain two codebases and support releases for the classic Firefox by proving security patches to them.

Not to mention more headaches for web developers as yet another browser shows up with its own bugs, differing support for standards like HTML5 and CSS3 etc.

Re:Everybody Hates Firefox Updates by maigret on Saturday July 07, 2012 @04:37AM (#4211136)
Funny, because two codebases exactly what Firefox is doing with FF 10 ESR, but without the renaming. So I don't find his proposition stupid, at the opposite. And come on, working on different codebases is a usual dev task, and every developer outside Facebook should know how to do that properly. Usually you have your shipped code and your development code, and you want to be at least able to ship a security fix without disclosing your new functionality. Concerning your last point, if you don't like that you are probably at the wrong place for web developments, where you should at least support a dozen different browsers. For enterprise software, that means one can just support 10 ESR instead of 1x and everything new that comes at each release, possibly breaking the application.