temeorr wrote:FF will not deallocate the mem once you open and close tabs.
But it does deallocate memory. Here's a pretty spectacular example. Fx was loaded up with huge Web sites, so it used 421 MB. The maximum memory use at any time was 30 MB for Fx itself. The rest was for actual data. Then the tabs were closed and it used only 22 MB plus 17 MB of cached data.
Here's another example. Loaded up to 180 MB total with random browsing. When tabs were closed, only 52 MB code + 20 MB cache remained. This one at least indicates a hint of a problem, but no one pursued it.
It's not necessary to shout. Just present your data. It's your turn. We want to see your numbers.
Just a couple of rules. Please read those two links first, so you know the pitfalls of measuring memory use in a Windows environment. Note also that a lot of people confuse cached data with failure to deallocate memory. And please use a new profile and use RC3. I don't want to argue about random extensions or a version that will be outdated in less than a month.