Francesco Presel wrote:
I have just been forced to kill and restart SeaMonkey after it ate up
most of my memory.
Today, I have opened far more many tabs than usual (I usually have 5-6
at a time maximum, but I had to do some image researches on the web and
to keep many results open at the same time).
Every now and then, I closed all those extra tabs, opened some new, ...,
and in the meantime the computer got slower and slower.
I finally closed all tabs but 6, but the computer was still slow; from
the system monitor it came out that SM was using 2.6 GB of memory!
After restarting and restoring the same 6 tabs, it was using just 300MB
of memory (which is what SM uses on average on my computer). So, what
were the other 2.3 GB used for? It looks as if SM does not properly
deallocate memory when tabs are closed
Technical info: Linux 64bit, using SM 2.7.2 64 bit (from Ubuntuzilla
repo); total RAM 3.2GB + 4.7 GB swap
Francesco, this grabbing and not releasing RAM problem has been known of
for quite a while and a solution is yet to be found.
While reading this post, and being aware that Mozilla/Firefox/SeaMonkey
are known to have problems letting go of memory, I was just thinking...
Cache.. As the website content is downloaded is it stored in RAM as well
as on disk?...Is this why Moz, FF & SM seem to absorb more and more RAM
as a session continues??
Does MSIE also store in RAM and Cache? If so, why doesn't MSIE also
suffer this problem?? Or does it, but no-one mentions it??
Probably just ramblings that the Mozilla developers have already
considered!!
--
Daniel
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
