FireFox.. A CPU Hog Suddenly

Horizon_Brave · 2016-07-09 22:33:27

Hey all,

So I only sort of recently upgraded to finally using the newly accepted Firefox branded web browser. Since the upgrade though I've noticed that it's been choking my cpu usage like Charles Manson at a county faire
Here's a screen shot below.

What happens is, if I open up any flash media (youtube I've noticed this on), the cpu usage spikes up as per normal. But if the computer goes into suspend/sleep and I wake it up and log back in... The cpu has been suffocated usually way above 100%, and there's usually a nice warm friendly message saying that a script in firefox has gone unresponsive and gives me the option to kill it, let it continue or debug it. As shown below:

Basically once I kill firefox (the x-www-browser process in the image below). It should be noted that this wasn't really happening with Icedove.
I tracked the 'unresponsive script issue where it can be configured in the about:config > dom.max_script_run_time
So you can set the time frame of how long firefox takes to notice and warn you that a script is spiraling out of control. The problem is even if I set it very very high, the performance is so degraded, that firefox is pretty much unusable. The cpu usage would be like 150% at that point, and whatever video you were attempting to watch, or was playing as long died.

So my main question I suppose is, has anyone else noticed this uptick in cpu usage since upgrading?

Sector11 · 2016-07-10 01:23:49

And you are hot on the heels of:

Index » Scripts, Tutorials & Tips » HowTo: Speed up Firefox

Which also talks of CPU 'abuse' - mine frequently hit 100% opening and closing FF.

EDIT: And today FF is doing the same ... maxing out a CPU at 100% so my HowTo isn't a howto!

Hoping to see something here.
Sorry what looked like a highjack.

Horizon_Brave · 2016-07-10 23:17:36

Mine has blown past 100% . I've seen a record high of 161% at it's peak. During this the laptop is worryingly hot, and performance slows to completely un-usable. Also take a look at the screen shot below, it shows that firefox also is using this plugin-container process which appears when you're using the flash plugin built into Firefox...again I don't think I experienced this in Ice-Weasel.
When you kill the plugin-container process, whatever videos/scripts/ads that were using it in FIrefox all crash and you have to reload the page to get it to restart...Of course doing this restarts the problem as well. Quickly, CPU usage will spiral out of control again.

Horizon_Brave · 2016-07-10 23:19:19

Whoops...forgot the screenshot.... here it is.

So I'm not sure how to debug this. Is this just indictive that my CPU / video card just isn't equipped to handle flash? Or is there something wrong with how F.F is handling this?

Sector11 · 2016-07-10 23:42:44

Yea, that's not good I have my thread here, do you see the same thing as well?

Neither of these bodes well for FF ESR

EDIT: I don't hibernate so don't run into the issue you have and running videos isn't a problem either

hhh · 2016-07-10 23:48:12

Does this happen with Mozilla's Firefox and Adobe's Flash too, or just with Debian firefox-esr and flashplugin-nonfree? I have no issues using Mozilla's Firefox and Adobe's libflashplayer.so...

hhh · 2016-07-10 23:49:26

^ Oops, YouTube is probably using HTML5, but flash is working w/out issues too.

Horizon_Brave · 2016-07-11 00:28:54

I see, generally, the same behavior. Out of curiously what cpu/memory/ year and model of PC are you seeing yours with? I'm running slightly older hardware an AMD64 dual core... about 2 gigs of memory, all on a MSI netbook from roughly...2008 ish?

hhh · 2016-07-11 01:22:31

Lenovo T500, 2G RAM, 32 bit.

https://support.lenovo.com/us/en/documents/pd001301

Also from circa 2008.

Head_on_a_Stick · 2016-07-11 06:42:06

Horizon_Brave wrote:

if I open up any flash media

I recommend not using FlashPlayer.

Do you have this problem with Google Chrome Stable?

Which FlashPlayer are you using with Firefox?

sudo update-flashplugin-nonfree --status
sudo update-pepperflashplugin-nonfree --status

Horizon_Brave · 2016-07-11 18:15:40

HoaS, I don't have google chrome installed, and probably would like to avoid switching over at this point if it can be helped... But I will indeed try dumping the use of flash and try pepperflash... Does Firefox-esr able to make use of pepperflash natively, or would i need to download a pepperflash plugin for firefox as well?

I'll try this in a few..

Head_on_a_Stick · 2016-07-11 18:20:43

https://wiki.debian.org/Freshplayerplugin

unklar · 2016-07-11 19:23:20

@Horizon_Brave,

please do ensure that FF-ESR on not

x-www-browser

is started.
Your screenshots say exactly.

mine

Horizon_Brave · 2016-07-11 19:51:54

unklar wrote:

@Horizon_Brave,
please do ensure that FF-ESR on not
x-www-browser
is started.
Your screenshots say exactly.
mine
https://cdn.scrot.moe/images/2016/07/11/ff-esr.th.png

unklar, I'm not sure why that would matter, my debian-alternatives is set for firefox-esr as the primary (and only) alias for x-www-browser.

Also, when I'm running pepperflash (freshpepper cause of firefox) and I go to a site that requires a flash plugin is it normal for it still to reference it as adobe flash? Look below:

notice how the error still says adobe flash I'm assuming this is just a browser oversight though.

I removed all instances of adobe, and disabled shockwave in the firefox browser.

Head_on_a_Stick · 2016-07-11 20:35:20

Horizon_Brave wrote:

is it normal for it still to reference it as adobe flash?

Yes, see https://en.wikipedia.org/wiki/Google_Na … ent#Pepper & https://en.wikipedia.org/wiki/NPAPI#PPAPI

unklar · 2016-07-11 20:47:39

Horizon_Brave wrote:

unklar, I'm not sure why that would matter, my debian-alternatives is set for firefox-esr as the primary (and only) alias for x-www-browser.

Perhaps that is the alternative (alias) still points to the wrong flash
or your paths are incorrect.

The right container does not cause high cpu utilization.

Horizon_Brave · 2016-07-11 21:00:48

unklar wrote:

Horizon_Brave wrote:
unklar, I'm not sure why that would matter, my debian-alternatives is set for firefox-esr as the primary (and only) alias for x-www-browser.
Perhaps that is the alternative (alias) still points to the wrong flash
or your paths are incorrect.
The right container does not cause high cpu utilization.

It's not, but just as a sanity check, I removed the x-www-broswer alternative, and added the direct path to /usr/bin/firefox-esr

Anyway Can someone post what their plugins look like in firefox? This is mine:

I want to compare with a working version because whennever I go to a flash page now, it says Flash Player Missing.

The current contents of /user/lib/mozillla/plugins:

mothra@mothra:/usr/lib/mozilla/plugins$ ls
flash-mozilla.so  libfreshwrapper-libpdf-backend.so  libfreshwrapper-libpdf-frontend.so  libfreshwrapper-nacl.so
mothra@mothra:/usr/lib/mozilla/plugins$

hhh · 2016-07-11 21:11:27

Firefox from Mozilla and libflashplayer.so from Adobe. I also use chromium quite a bit, but if a page insists on Flash I use FF. Flash entry in about:plugins...

Shockwave Flash

    File: libflashplayer.so
    Path: /home/hhh/.mozilla/plugins/libflashplayer.so
    Version: 11.2.202.626
    State: Enabled
    Shockwave Flash 11.2 r202

MIME Type	Description	Suffixes
application/x-shockwave-flash	Shockwave Flash	swf
application/futuresplash	FutureSplash Player	spl

Contents of ~/.mozilla/plugins (create the folder)

libflashplayer.so

The reason I use this config is because as soon as the plugin is outdated, Firefox blocks the content with a warning and offers a link to Adobe to see if a fix has been issued. No waiting for Debian to catch up (though they do very well).

Same with Firefox, the versions Mozilla serves automatically check for updates every time they're executed.

https://forums.bunsenlabs.org/viewtopic.php?id=1385

https://forums.bunsenlabs.org/viewtopic … 083#p32083

Horizon_Brave · 2016-07-11 21:48:48

hhh, any reason you don't use this whole pepperflash/freshpepper with firefox? It's what i'm trying to lean towards. Since I think the adobe libflashplayer.so seems to be causing the issue in my OP

hhh · 2016-07-11 21:56:51

I've been using this setup since before I created that HowTo. I got tired of how Debian was handling Firefox and I hated how they implement flashplayerplugin-nonfree. Browsers are buggy things at best, I decided to cut out the middleman. In my case, I've found it to be a thousand times better.

On a new install, I skip flash in bl-welcome and just create the plugin folder locally and download straight from Adobe. I've never had the CPU issues you're posting using stock jessie firefox or iceweasel, flash from adobe and the uBlock origin addon.

Anyway, uninstall that hot mess you have going and try my HowTo, you can always switch back.

#1 2016-07-09 22:33:27

FireFox.. A CPU Hog Suddenly

#2 2016-07-10 01:23:49

Re: FireFox.. A CPU Hog Suddenly

#3 2016-07-10 23:17:36

Re: FireFox.. A CPU Hog Suddenly

#4 2016-07-10 23:19:19

Re: FireFox.. A CPU Hog Suddenly

#5 2016-07-10 23:42:44

Re: FireFox.. A CPU Hog Suddenly

#6 2016-07-10 23:48:12

Re: FireFox.. A CPU Hog Suddenly

#7 2016-07-10 23:49:26

Re: FireFox.. A CPU Hog Suddenly

#8 2016-07-11 00:28:54

Re: FireFox.. A CPU Hog Suddenly

#9 2016-07-11 01:22:31

Re: FireFox.. A CPU Hog Suddenly

#10 2016-07-11 06:42:06

Re: FireFox.. A CPU Hog Suddenly

#11 2016-07-11 18:15:40

Re: FireFox.. A CPU Hog Suddenly

#12 2016-07-11 18:20:43

Re: FireFox.. A CPU Hog Suddenly

#13 2016-07-11 19:23:20

Re: FireFox.. A CPU Hog Suddenly

#14 2016-07-11 19:51:54

Re: FireFox.. A CPU Hog Suddenly

#15 2016-07-11 20:35:20

Re: FireFox.. A CPU Hog Suddenly

#16 2016-07-11 20:47:39

Re: FireFox.. A CPU Hog Suddenly

#17 2016-07-11 21:00:48

Re: FireFox.. A CPU Hog Suddenly

#18 2016-07-11 21:11:27

Re: FireFox.. A CPU Hog Suddenly

#19 2016-07-11 21:48:48

Re: FireFox.. A CPU Hog Suddenly

#20 2016-07-11 21:56:51

Re: FireFox.. A CPU Hog Suddenly

Board footer