 Originally Posted by Ynot
They're not memory leaks (seriously)
it's the cache
while any modern, complicated piece of software will invariably leak memory due to programmer error, usually it's a minuscule amount of memory (and therefore overlooked - big memory leaks get noticed and fixed quickly)
It irks me when people complain about FF leaking vast amounts of memory
It's the cache
each tab caches the last 5 pages in the history
(based on the anonymous usage statistics thing that you can opt-into, mozilla reckoned 40% of all page navigation was re-navigations to pages visited less than 10 pages ago)
Each tab caches (by default) the last 5 pages
So, you have 15 tabs open, all with a history....
you can change the page caching if it's not suitable to you
Yes, but let's say I have 20 tabs open, then close them down to maybe 4... it never releases the memory. I've seen it sitting at 700MB indefinitely before I put it out of its misery and restarted it. And to be honest, I think even "miniscule" memory leaks are unacceptable in any mass-distributed software. It might not be a launch-blocker, but it better be addressed, and in a hurry.
It also crashes more than it should (i.e. almost never). That might be due to extensions, though, but the memory issues are just... bleh...
I just worry that FF is really starting to drown in feature creep. Ironically, that's the whole reason why it was branched from the Mozilla project in the first place. Really, it doesn't need new built-in features for a long while... thanks to the extensions, you could spend months on a feature freeze and still see all kinds of cool extensions come out.
|
|
Bookmarks