Firefox memory hog

[swazi]

Hi

As my uptime grows, so does my swap. How come the buffers/cache does not get used up first? and then swap? Ok i have 50 tabs open on average in Firefox at any given time and Firefox uses 23% of my memory.

free
total used free shared buffers cached
Mem: 4023796 3904924 118872 0 132860 623836
-/+ buffers/cache: 3148228 875568
Swap: 4088504 127696 3960808

My uptime is only one day or so after the kernel update, as of now, but once my uptime reaches over 10 days, my swap rockets.

[marja]

Hi Swazi,

This thread was viewed 48 times until now

I don't know what a "memory hog" is, but from what I read the meaning of "hog" here has something to do with the second meaning here: http://en.wiktionary.org/wiki/hog#Noun "A greedy person; one who refuses to share."

And I don't know the answer to you question, I'm just curious to know whether your swap wouldn't rocket when you go to "Edit"»"Preferences"»"Privacy"»"History" and set Firefox to never remember history.

But I suppose your problem already got solved, anyway?

[wilcal]

Have you noticed that Linux in general
will tend to toss things, everything,
into unused memory? That to speed things
up. I have a Mageia 1 64-bit system 16GB
DRAM. If I use it long enough, without
logging out and back in again, Mageia,
really Linux, will toss whatever comes
across the Browser into memory. It's not
hogging memory just using a resource that's
not being used.

My always on line up and running server,
a Mandriva 10.2 system w/4GB DRAM and the
system I am using now, has used up all of
its DRAM. Everything. That's because it's
on all the time. If I reboot things go
back down to nothing then again slowly
as I surf the Internet over a few days
consume whatever DRAM is available.
Things never slow down. If ever more
DRAM is needed for apps the stuff in
memory cache is written over.

[doktor5000]

The statistics you show above say that your swap is nearly completely empty and your ram is all used.
I see nothing special or problematic there? Buffers and cache are a part of the used memory, BTW.