You've got 100 processes running. It looks like you've got a lot of third party stuff running in the background.

I have only 36 with FF running - 2 for FF and 2 for AdAware- the remaining 32 are mostly Windows.

Only one tab. I tried the FF 13 beta and it's working fine to me, i hope when the final version comes out there's no big changes..

I have two windows open right now and have been hopping all over the place on the Internet all morning. I'm at 225K with FF and 62K with plugins. Note your Firefox and Plugin container sizes. I took this capture with no keyboard activity.

I'll stick with what works for now until people quit having massive problems with 12 then consider upgrading. If it ain't broke, I ain't fixing it.

MikeWilson Thanks for your posts, but please remember firefox 9 is not secure if you are happy to take the risks so be it.

If you would lie to try to get your system working with the current Firefox Release (currently fx 12), or find out which add-on; or whatever; caused the problems when you use firefox 12 then please start a new thread. (And post here when you do so. I am sure all many readers will be interested in the results).

I strongly suspect problems will turn out to be with other software interactions and will not get fixed by Firefox changes.

It is probably incorrect to sate

I'm NOT having any security, crash, memory leaks or any other problems

because Firefox 9 is intrinsically NOT secure. The fact you are using security software is not likely to remove all risks.

You have already suggested that the latest version of AdBlock may be one of the problems.

You say

Next was upgrading to 2 Gig of ram and turning off the PAGE FILE. This lets FF run out of RAM instead of the hard drive and eliminates a lot of fragmentation on the HD from heavy surfing. This also solved memory leak problems. 

Increasing to 2GB of ram is probably a good move for a variety of reasons.

Note on some Windows systems, I believe, setting page file to a fixed maximum size, rather than a variable range may reduce fragmentation of the page file itself. Firefox, and systems in general will slow down when using a page file rather than RAM, but that does not necessarily mean having no page file is always good. This is however leaning towards being a discussion relating to OS tweaks and not appropriate to this forum.

Transferring cache to a flash drive, or for that matter even another HDD spindle could speed things up, but again not really on topic for this forum. Disabling unused plugins, and stopping unused background applications is again good general advice, that you have given.

Fragmenting the HD where FF may be operating out in virtual memory of is a problem, one which I solved by removing the CACHE to flash drive and the other by taking control of Windows lousy memory management. I have photos on main site. Spybot has its own internal browser security for both IE and FF.

To each his own. This old Dell Optiplex 270 with 2 Gig of RAM runs like a bat out of hell even with FF. I still sticking with what already works instead of trying to debug FF12. I am also sticking with my statement about not having any of the aforementioned problems since I'm no having them. My Task Manager somewhat speaks for itself.

Vipanonymous,

Great to hear that you are having no problems after changing from Firefox 12 release to Firefox 13 beta.

That presumably will also have resulted in use of a new profile and possible extension changes, factors that may themselves contribute to a solution. Note Firefox 13 is due out early next month as the Release.

As a general note my personal opinion is that it using the Beta channel almost routinely could be a good idea. A big advantage is that once you are on it and have had it for a couple of months you will always have the knowledge that
if you run into a problem you have a downgrade option because it is relatively easy to install the Release version and you will have already tried that while it was in beta and can be fairly certain it will work flawlessly,

Once Firefox comes out with something that people aren't complaining about everywhere, I'll check into it - online reviews.

Rushing into something like all the people buying phones when they first hit the market then taking them back by the truck loads, happens all the time. If 13 turns out to be pain, I can always reinstall 9.

A large majority of problems here seem to be with FF12. It's looking like Windows Vista - too buggy.

This entire forum is full of problems with people who recently upgraded to version 12. Google also shows pages full of others having the same problem. Most of the info here and there shows problems being resolved with 13 Beta.

I wouldn't waste my time experimenting with 12 if it's that big of a widespread problem. Try 13 and see if its as a good as 11 or better. If you still have problems with 13 and had no problems with 11, then go back to 11 until Firefox gets the kinks out of everything.

It should be noted that with my current setup, I can watch memory decrease back to original amount as I close out windows and leave Yahoo email open.

I do agree it is worth trying the beta channel

• http://www.mozilla.org/en-US/firefox/channel/#beta/beta-desktop

The problem may be being resolved by the new profile used in Firefox beta, if that is the case the standard Firefox 13 may not resolve the problem whereas for instance creating and using new Firefox 12 profile may solve the problem now.

• basic troubleshooting_8-make-a-new-profile

Lets remember this only affects a very, small proportion of the nearly 1/2 a billion users. It may still affect a lot of users but probably as a common symptom of several varied problems. Doing nothing will not result in a magic fix.

Disabling JAVA next generation reduced my usage from 400M+ to 130M Control panel > Java > Advanced > Java plug-in > next gen

Thanks to the posters who suggested this ! https://support.mozilla.org/en-US/questions/927004

Win2k FF 12 Java 6.0.31.5 AB+ FB NS Foxit VLC

I have been having these issues as well. Firefox memory usage will balloon insanely high (2-3GB after a few minutes of light browsing). Sometimes it will drop back down to a more reasonable level (a few hundred MB), sometimes it hangs (presumably while trying to garbage collect everything), and sometimes it crashes in the garbage collection code (https://crash-stats.mozilla.com/report/list?signature=js%3A%3Agc%3A%3AMarkChildren%28JSTracer*%2C+js%3A%3Atypes%3A%3ATypeObject*%29).

I was able to capture an about:memory report when Firefox had gotten to about 1.5 GB and have attached an image.

Don't know if any of this helps or not. I'm looking forward to trying Firefox 13 when it comes out.

hello dharding, we can probably offer you better help, when you open your own question and provide more detailed information about your system (copy it from help > troubleshooting information).

tackling memory leaks in the browser is a top priority of mozilla & much progress has been made over the last months. such high memory consumption as you've described is most commonly caused by leaking addons & plugins nowadays...

Created a new question: https://support.mozilla.org/en-US/questions/928367.

thank you, will post my suggestions there!