[Urgo]

* Drastically improved memory handling for certain use cases

^^ apparently not the use cases I use. FF7's been running for about 12 hours on my win7 box and is using over a gig of ram just like normal...

It started off good but then just kept growing over the hours. Nothing really improved here. :(

[nailer]

> FF7's been running for about 12 hours on my win7 box and is using over a gig of ram just like normal...

Are you looking at resident set size (aka real memory), versus virtual set size (aka virtual memory)?

The memory VMs in both Windows and Linux kernels will happily let an app malloc all they want until they hit the userspace address limit, with no affect on performance. It's only when those apps use the memory that there's a perf hit.

[gcp]

Be sure to enable this:

* Added an opt-in system for users to send performance data back to Mozilla to improve future versions of Firefox

Some of these issues are very hard to reproduce for the developers. If users like you turn it on, there's hope of actually getting it fixed.

[gkoberger]

What add-ons are you using? 95% of the time, problems with Firefox (speed, crashing, oddities) can be blamed on a slow add-on.

[kinetik]

Open about:memory and see where the memory is going. And if you think the use is excessive, please file a bug including the about:memory data and any details you know that would aid in reproducing the problem.

[grimoire]

Is this memory that is needed for some other application you are running? Is your system running low on virtual memory? If not, what is the problem with FF using it? From what I've seen (at least with FF6), when system memory gets low FF will start to release memory back.

I'd rather have FF use the memory for cache to speed up performance than to have it sit unused.

[Garbage]

Try going to "about:memory" -> "Minimize Memory Usage"