Linked by David Adams on Wed 3rd Aug 2011 16:50 UTC, submitted by _xmv
Mozilla & Gecko clones Mozilla Firefox has been listening to recent memory complains, and as a side effect tested the browser's scalability to the extreme with memshrink's improvements. The results are shocking: For 150 tabs open using the test script, Firefox nightly takes 6 min 14 on the test system, uses 2GB and stays responsive. For the same test, Chrome takes 28 min 55 and is unusable during loading. An optimized version of the script has been made for Chrome as an attempt to work-around Chrome's limitations and got an improved loading time of 27 min 58, while using 5GB of memory.
Thread beginning with comment 483346
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Comment by Praxis
by Pro-Competition on Wed 3rd Aug 2011 17:51 UTC in reply to "Comment by Praxis"
Member since:

... I have always found firefox to use more and more memory as the day goes on, while chrome keeps going back to the baseline memory usage. When Firefox fixes that memory problem I want to read a blog post on that.

That was exactly my first thought, also. Fortunately, about a month earlier on the same blog, we have:

The changes won't be in FF6, but will be in FF7.

Reply Parent Score: 2

RE[2]: Comment by Praxis
by Erunno on Wed 3rd Aug 2011 18:46 in reply to "RE: Comment by Praxis"
Erunno Member since:

And that's not even the end of it. Under the leadership of Nicholas Nethercode Mozilla is making a strong push towards reducing Firefox' memory usage as much as possible without sacrificing performance. Further memory reductions are already in the pipeline for post-FF7 releases. The best place to follow the effort is by reading Nethercote's weekly MemShrink progress reports on his blog:

Reply Parent Score: 2

RE[3]: Comment by Praxis
by WereCatf on Wed 3rd Aug 2011 19:17 in reply to "RE[2]: Comment by Praxis"
WereCatf Member since:

The strange thing is that...well, people have been telling Mozilla devs for YEARS that Firefox is eating up way too much memory, and they've just denied the whole thing all this time. So, are they now admitting that they've been in denial, or are they claiming that Firefox has just now very recently started doing that?

Reply Parent Score: 3