flyguy wrote:
You may want to disable any add-on or try SM in safe mode. Or perhaps
upgrade your version of SM.
I am using Adblock Plus, disabled for the alternet.org site. If I select
"disable everywhere", the cpu usage goes from 60% to 40-50%. Disable the
extension and cpu usage goes to ~20%; closing the alternet.org tab takes
it to ~8%.
So, something about the alternet.org site makes SM 2.49.4 busy, having
Adblock enabled makes SM very busy, even if it's disabled for that site.
That seems odd. Should I be using a different adblocker? Or just disable
it for troublesome sites?
If you're running Seamonkey 2.53.1, be aware that the release notes
indicate that there's no current version of AdBlock Plus that's
supported. For that kind of functionality, there is still uBlock
Origin, where the dev continues to keep support for an XUL version.
Take a look at
http://www.seamonkey-project.org/releases/seamonkey2.53.1/ and note that
version 2.9.1 of Adblock Plus is known to cause memory and CPU issues,
and it is recommended to switch to uBlock . I did that about a year
ago, and I've found that while it took me a while to get used to
uBlock's different philosophy and UI, I generally like it better than
Adblock.
Moving to uBlock may solve some of your problems, but perhaps not
everything, especially if you have lots of blocking rules in place.
I've found that I occasionally have resource issues, especially if I
leave Seamonkey open overnight (and I normally leave my machine running
24/7). When that happens, Seamonkey tends to become less responsive,
and a check of the Windows task manager shows lots of CPU activity and
memory usage in excess of 1.5 GB. A few days ago, I was filling out a
form that had a lot of entries (and where every entry had script
processing). By the time I got to the end of the form, the last few
entries were giving me script timeout errors.
I do make quite a bit of use of extensions, but most of them are small.
However, with the combination of uBlock and NoScript active, I'm
inclined to believe that those (either individually or together) are the
primary culprits. I have been long suspicious of the possibility of
memory leaks, but that's only a guess. Last summer, I changed out my
machine -- it has 16 GB of RAM in it and an SSD drive, and the high
resource usage problem seems to be less. But I still have to remember
either to make sure I close Seamonkey at the end of the day, or if I
start the day and find it open, restarting before beginning working.
Smith
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
