Le 6 juillet 2010, PeterAntonRev a écrit :
Here are the details fo my memory problems.
As already mentionned by Ant, RAM is not CPU. Of course, if you open multiple pages, they're all somehow stored in memory. But once loaded they shouldn't "consume" CPU anymore.
I'm using Seamonkey ver. 2.0.4. As I open and close tabs, or basically just use my browser the available memory gradually decreases until it's down to 10% or less. At this point my system becomes so slow that I have to do something about it. I've watched the memory as I close each window full of tabs. (I use SpeedItUpFree memory manager to watch the memory.) Each closed window adds a little to the available memory until it reaches 25% or so. Upon closing the last window the memory shoots all the way up to 70% or 80%, so it looks like it's the core Seamonkey module that is to blame, not individual windows or tabs.
Looks like a cache matter to me, but I'm no expert: maybe previously loaded pages remain in memory cache until you quit. Have a look at about:cache?device=memory to check.
-- LL _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
