On Jul 5, 12:55 am, Ant <[email protected]> wrote: > Hi! > > Is it me or does Mozilla's SeaMonkey v2.0.x seems to hog CPU a bit if I > have like 20+ tabs at once (yes, I am that crazy)? I noticed > seamonkey.exe crawls to hiccup speed (up to 0%-25%) even on a quad-core > system with 2 GB of RAM in an updated Windows XP Pro. SP3. I even notice > this sometimes in a fairly new 64-bit W7 machine on an Intel i5 machine. > I reproduced this inhttp://www.neatorama.com/(by itself with 40+ tabs) > and others (numbers can vary but many tabs), and I don't see anything > fancy running like animated graphics/videos. > > I do use the latest versions of Flashblock, Adblock Plus, etc. I did > notice Process Explorer shows > seamonkey.exe~jsj_JavaInstanceMethodWrapper even if I am not doing > anything (idled). I don't even have Java enabled! SeaMonkey just spikes > on its CPU. Memory usages can go high like peak memory usage to 408,280 > K and its VM size went to 239,452 K according to Task Manager. > Restarting and restoring sessions did not help either. > > Thank you in advance. :) > -- > "Any spoke will lead the ant to the hub." --unknown > /\___/\ Phil./Ant @http://antfarm.ma.cx(Personal Web Site) > / /\ /\ \ Ant's Quality Foraged Links:http://aqfl.net > | |o o| | > \ _ / If crediting, then use Ant nickname and AQFL URL/link. > ( ) If e-mailing, then axe ANT from its address if needed. > Ant is currently not listening to any songs on this computer.
I don't think you're crazy. I have had the same problem for a long time. I have been going on the assumption that a tab is just another instance of a window, but someone mentioned that tabs are to blame. Apparently the coding for tabs manages memory differently than windows. I haven't done an experiment to open up numerous windows to see if that causes the same problem. Has anyone done this??? Here are the details fo my memory problems. 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. I also have used the memory management feature of SpeedItUpFree and recovered some memory, but it doesn't work as well as simply closing Seamonkey down now and running it again. There are, of course, times when Seamonkey 2 freaks out and then I reboot my system. It's an imperfect situation, but I'm glad there is a relatively simple way to get things running smoothly again until the next meltdown. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
