This bug fix won't make much of a change right after starting Firefox, it just prevents memory from building up over time due to closed tabs. Additionally it's effective in nightly builds not beta, so 15.0a1 not 13.
Your comparison is useful overall, but not relevant to this change.
Re:Firefox finally plugs the leak
by robin_reala on Tuesday May 08, 2012 @08:45AM
(#3943319)
Realised that after I posted. Still, as you said this shows that Firefox has come a long way since the 4 days.
Re:Firefox finally plugs the leak
by keeperofdakeys on Tuesday May 08, 2012 @10:26AM
(#3943756)
With Firebug installed, you most likely have JIT disabled http://antennasoft.net/robcee/2009/12/15/firebug-and-the-jit.... I would suggest you use a separate 'webdev' profile for such things (the inbuilt web console that is now in firefox is also getting there).
Re:Firefox finally plugs the leak
by robin_reala on Tuesday May 08, 2012 @10:37AM
(#3943811)
That was true in 2009 but was fixed in January 2010: https://bugzilla.mozilla.org/show_bug.cgi?id=534120#c52 (although it’s true that if you’re actively debugging scripts the JIT turns off - Firebug has the script panel off by default)
Incredible, I've been doing all my browsing for the past year with the script and console panels activated and had no idea that it was disabling the JIT for every page that I visited. Just turned them off, and I can't believe how accustomed I'd become to sluggish webpages. Thanks for the link!
Thanks, that's great to know, time to give the latest FF another go.
Re:Firefox finally plugs the leak
by robin_reala on Wednesday May 09, 2012 @08:41AM
(#3948235)
If you haven’t done so already, it’s probably worth killing your old Firefox profile and starting completely anew.
The internal memory measurements (about:memory) come out as 835mb resident for Chrome, and 324mb (of ‘explicit’, whatever that is) for Firefox.
I’m not using any extensions in Chrome. In Firefox I’ve got installed Firebug, FireFontFamily, FireQuery, Lastpass, PDF.js and QuickJava.
Edit: oops, missed cloning a tab with a video in over to Chrome. That explains the disparity in Flash, and you could probably expect to increase Chrome’s real mem usage a little had I not closed it already…