Originally Posted by FewMiles
100k, no way!
Seriously, I find that simply quitting and restarting firefox will do the trick. The memory/cpu hogging issue seems to me (though I'm not certain) to be related to plug-ins like Java, Flash, etc. Closing the browser also unloads the plug-ins and seems to put things back to normal.
FewMiles..
this CAN actually happen, but most usually when using TABed browsing in FF. Every new tab consumes about 10K more in memory. Sometimes a bit less, sometimes more. problem is, when a window is opened that runs the JAVA engine, that boosts it up about 40K, so 20-30K base, plus 10K a window and then BOOM 40K for a window that is running JAVA.
I have had well over 100K on FF sometimes, I know then I am opening too many windows. I try to keep it to under 10 open windows at a time.