On 2/28/19, Ant via support-seamonkey <[email protected]> wrote: > On 2/27/2019 4:29 PM, Paul B. Gallagher wrote: > ... >> I did have some trouble this afternoon as I was perusing Google News. >> For some stories, I clicked "View full coverage" and each time I did, SM >> hung. As before, CPU peaked at 26–27% and RAM usage was a little over 2 >> GB. After two or three minutes, the cursor returned to its usual arrow >> shape and CPU usage fell to under 10%. But the next time I clicked "View >> full coverage," it was like standing on the brakes again. > > http://news.google.com, http://linkedin.com (logged in), > http://facebook.com, etc. are SO slow and bloated in SM esp. with > multiple tabs :(
Try it using either noscript + request policy continued or ublock origin + umatrix https://www.cnet.com/news/ad-blocking-brave-gets-memory-advantage-over-chrome-on-news-websites/ Lee _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
