On 2015-06-03 19:16, cmcgrath5035 wrote:
>
> I have 13.2/KDE 4.14.6 running with Firefox 38.0.1
>
> I tend to be a bit ‘sloppy’ with my browser these days, keeping 10-12
> tabs open to speed bouncing about on various topics.
> Over the past couple months I have experienced, with increasing
> regularity, periods in which Firefox appears to have stalled or frozen.
> I usually have KSystemMonitor open, and during these stalls see Firefox
> consuming 25% or more (likely a full core, of 4) doing what it is doing.
>
> i’ll add that ever since Mozilla switched to Yahoo as the default Search
> (but I still use Google, so this is a version marker) , I see al lot
> more unblockable Pup-Ups and nuisance adv activity. If I had to, I would
> somewhat correlate this issue with the version that made the Yahoo
> switch, but I don’t recall the release #.
I have two addons on firefox: Flashblock (version 1.5.18 currently) you
should have: it blocks ALL flash animations till you click on an arrow
the addon displays on placeholders. Flash is a very likely candidate at
high cpu load.
The second one is “addblock plus”, currently version 2.6.9.1-signed,
which can be used to block the worst commercial (or all). The available
filters are listed here https://easylist.adblockplus.org/en/
I don’t block all commercials, only those that are intrusive. And I make
exceptions on some org pages, I understand they need to make a living. I
block popups or floating banners and such.
Notice however that addblock adds memory ussage. Possibly a lot,
depending on the pages. It also slows down page loading, because it
breaks parellelization: pages elements have to be fully downloaded and
examined before each element in them is allowed to load and display, or
blocked.
Some info on this:
https://blog.mozilla.org/nnethercote/2014/05/14/adblock-pluss-effect-on-firefoxs-memory-usage/
https://adblockplus.org/blog/on-the-adblock-plus-memory-consumption
http://www.reddit.com/r/programming/comments/25j41u/adblock_pluss_effect_on_firefoxs_memory_usage/
page with 400 iFrames, With ABP, needs 1960MiB
http://vimcolorschemetest.googlecode.com/svn/html/index-c.html
One very interesting post:
++++—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-
Chrome Dev here. We see this (and much more) with chrome as well.
Adblock, noscript, ghostery, and other addons like them cause 90% of the
issues we see in the forums.
At the very least, by running any of these you are:
Increasing memory usage anywhere from 10% to 30%
increasing overall cpu usage across all cores
increasing overall load time of the page by about 15% to 50%
completely screwing many of the optimizations that have gone into
the browser, effectively making the multi-threaded nature of the browser
fight itself.
This is because these programs need to interrupt any and all http calls
to check them against a big list of “no-no” domains held in memory. If
it matches, they remove the element from the dom so it doesn’t load and
let the browser continue.
This has the effect of making every single thread sync up each time the
dom is updated, so these extensions can scan the new elements to ensure
they aren’t loading ads/scripts. Fancy stuff like threaded compositing,
network predictors and prefetchers, and batched layout rendering are all
abandoned when any one of these is in play.
—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-—-+±
>
> I keep Firefox up to date, from the openSUSE-13.2-Update repo
>
> Anyone else experiencing this?
> In an attempt to investigate, I moved several almost always open tabs
> over to Chrome.
> That helped a little, Chrome does not seem to have the same issues. I
> have tried selectively closing some of the Firefox tabs, but the stalls
> continue.
>
> Any thoughts on how to better diagnose?
Try about:healthreport, about:buildconfig, about:memory… what it
doesn’t have is a CPU load one, specifically one that shows the load on
each tab (Chrome does have a CPU display page - try Shift + Esc).
I also miss a view or lists of all open tabs.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
