Jump to content


Photo

webclient has huge CPU usage in FF

CPU usage firefox webclient cpu

  • Please log in to reply
20 replies to this topic

#1 daedalus OFFLINE  

daedalus

    Advanced Member

  • Members
  • 1320 posts
  • Local time: 11:46 PM

Posted 19 January 2017 - 04:40 PM

i noticed that every page of the webclient opened in Firefox is maxing out the CPU (actually only one core cause FF cant use more)

it happens even on the login screen

 

this does not take place in Chrome or Edge

 

FF 50.1.0

server 3.1.278.0



#2 daedalus OFFLINE  

daedalus

    Advanced Member

  • Members
  • 1320 posts
  • Local time: 11:46 PM

Posted 28 January 2017 - 05:18 AM

really? nobody?

 

checked on 2 systems same issue



#3 jordy OFFLINE  

jordy

    Advanced Member

  • Members
  • 1370 posts
  • Local time: 07:16 AM
  • LocationAdelaide, Australia

Posted 28 January 2017 - 06:53 AM

deleted...


Edited by jordy, 28 January 2017 - 07:02 AM.


#4 jordy OFFLINE  

jordy

    Advanced Member

  • Members
  • 1370 posts
  • Local time: 07:16 AM
  • LocationAdelaide, Australia

Posted 28 January 2017 - 07:02 AM

Hey, Can confirm high cpu on FF when running the Emby WebUI from a remote client (Not the actual server pc) but on the same Lan.

 

Surface Pro 3 - i5 Dual Core

 

FF 51.0.1 (32 bit):

With Emby running: 29 - 30 % Cpu

Without Emby running: 3 - 4%

 

Chrome 55.0.2883.87 m

With Emby running: 3 - 4 % Cpu

EDIT: I should add that I'm running Emby Dev server 3.1.6235.2624.


Edited by jordy, 28 January 2017 - 07:05 AM.


#5 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 18503 posts
  • Local time: 02:46 PM
  • LocationWashington State

Posted 28 January 2017 - 04:49 PM

So would you consider this a Emby issue or a Browser issues?  As you have shown one browser is more efficient that the other.  It take Firefox a lot more processing power then it does Chrome.


Edited by Happy2Play, 28 January 2017 - 04:50 PM.


#6 daedalus OFFLINE  

daedalus

    Advanced Member

  • Members
  • 1320 posts
  • Local time: 11:46 PM

Posted 28 January 2017 - 04:59 PM

as mentioned in the first post this happens on all pages also the loginscreen or the dashboard

what processing power is needed there ?

 

and further the load (80-90% of one core) persists for hours if i just let the page open



#7 Happy2Play OFFLINE  

Happy2Play

    Trial and Error

  • Moderators
  • 18503 posts
  • Local time: 02:46 PM
  • LocationWashington State

Posted 28 January 2017 - 05:13 PM

Well we know all development is done around Chrome, then made compatible around other browsers.  So in the end every browser is going to have there own quirks.

 

For me testing FF, it is always cycling cpu 2-5% where Chrome is showing 0% on the same Emby page.

 

Navigating in FF bounces to about 45% then cycles back down to 2-5%.

 

Navigating in Chrome never went over 15%.

 

Overall for me Firefox has always used more resources.

 

In my Comparison I would blame Firefox not Emby.


Edited by Happy2Play, 28 January 2017 - 05:22 PM.


#8 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 153470 posts
  • Local time: 05:46 PM

Posted 28 January 2017 - 05:20 PM

For what it's worth in Firefox, my CPU spikes on a lot of sites.
  • Happy2Play likes this

#9 daedalus OFFLINE  

daedalus

    Advanced Member

  • Members
  • 1320 posts
  • Local time: 11:46 PM

Posted 28 January 2017 - 05:38 PM

Navigating in FF bounces to about 45% then cycles back down to 2-5%.

 

 

For what it's worth in Firefox, my CPU spikes on a lot of sites.

 

it does not spike nor come back to normal usage

 

the load (80-90% of one core) persists for hours if i just let the page open



#10 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 153470 posts
  • Local time: 05:46 PM

Posted 28 January 2017 - 09:20 PM

Well I see it go up a few % points but nothing like you're describing.



#11 Rominator OFFLINE  

Rominator

    Member

  • Members
  • 13 posts
  • Local time: 11:46 PM

Posted 29 January 2017 - 06:27 AM

same here CPU usage goes up on the Webclient since the last stable update.

on 3.1.2 everything was fine.



#12 puithove OFFLINE  

puithove

    Advanced Member

  • Alpha Testers
  • 718 posts
  • Local time: 04:46 PM

Posted 29 January 2017 - 09:16 AM

Try disabling all FF add-ons and see if that makes any difference.



#13 Abobader OFFLINE  

Abobader

    Super-Tester

  • Administrators
  • 9472 posts
  • Local time: 12:46 AM

Posted 29 January 2017 - 10:02 AM

Good day,

 

I did some test and as Luke said, some % view point when enter a page while browsing my libraries, but I can agree with everyone here, FF do more demand on the cpu than Chrome.

 

What in Chrome like 4% it on FF as 11% of cpu usage.

 

FF indeed make the cpu goes to 70% but it spikes matters, then go to like 15%.

 

So Chrome won on my test for easy on cpu.

 

My best



#14 daedalus OFFLINE  

daedalus

    Advanced Member

  • Members
  • 1320 posts
  • Local time: 11:46 PM

Posted 29 January 2017 - 10:06 AM

Try disabling all FF add-ons and see if that makes any difference.

 

surely i tested this on a fresh profile before and no makes no difference



#15 genesisforlive OFFLINE  

genesisforlive

    Advanced Member

  • Members
  • 93 posts
  • Local time: 11:46 PM

Posted 31 January 2017 - 03:10 PM

Hi,

when i use FIrefox as Browser, the CPU load when Emby is open is always at 25%

 

Emby Version 3.1.289.0 beta on WIndows 10

 

the Problem is on ah http and https connection

 

I think the problem has been a while

 

ps: no Problems on IE or Chrome

 

greets



#16 speechles ONLINE  

speechles

    Advanced Member

  • App Developer
  • 5972 posts
  • Local time: 02:46 PM

Posted 31 January 2017 - 03:17 PM

Firefox does this to me too, but mainly because firefox is downloading updates silently in the background. It does this all the time, download updates. Doesnt care what you are doing, or a schedule, when it has updates it downloads them. The PC fans whir up, you can tell if you use the resource monitor that it isnt related to emby. It is an svchost attached to firefox (not emby) eating up all the cpu. Firefox doesnt care to tell you it is downloading updates, it just tells you when you open firefox the next time "please wait" as it applies all these "updates" before it opens. This keeps getting worse and worse Ive noticed. The last update creates multiple firefox pid to sandbox threads. The super cool part, its more secure, but eats up even more cpu and ramps the cpu often until the fans get loud enough you investigate wtf is going on.

Tl;dr - This is mozillas attempt to migrate firefox users to any other browser.

Sent from my Nexus 7 using Tapatalk

Edited by speechles, 31 January 2017 - 03:27 PM.


#17 QuasiZ OFFLINE  

QuasiZ

    Newbie

  • Members
  • 7 posts
  • Local time: 04:46 PM

Posted 23 February 2017 - 12:12 PM

tl;dr: This is a known bug in FireFox that already has a fix, but that fix isn't available in the current version of FireFox. Read on for details and temporary work-around.

I'm not the biggest fan of FireFox either, but let's not start any baseless blaming of things on unfounded assumptions - especially when not in any position to actually offer any insight into the issue being reported.  /grump
  
The actual culprit here is in gamepadtokey.js .  Specifically, the call to navigator.getGamepads() .  You can test this for yourself by firing up a clean FireFox instance, open up Task Manager, open up the browser console, and just evaluate "navigator.getGamepads();" .  For FireFox (51.0.1 (32-bit) in my case), I instantly get 100% thread use (~16% total CPU on my machine, quad core + hyperthreading), which does not abate.
 
This appears to be a known issue in FireFox.
Bugzilla link: https://bug623317.bu....cgi?id=1318839
It's also already fixed, but apparently they're not yet ready to release that fix in a Stable copy of FireFox because it depends on some other fixes which have wider impact.
 
If you don't use a gamepad/controller for Emby, and you want to fix the CPU issue on your machine temporarily (instructions for Windows), find the .js file typically at:
c:\Users\YourUserName\AppData\Roaming\Emby-Server\System\dashboard-ui\bower_components\emby-webcomponents\input\gamepadtokey.js

Rename it, for example to:
gamepadtokey.js.bu

Then load this page into your browser (assuming default port): 
http://localhost:809...ey.js?v=3.2.1.0
 
Force a refresh without cache by pressing Ctrl+F5. This will make the Emby server realize that the file's no longer there.

Now refresh your Emby dashboard/web view, and your CPU should no longer be under load while Emby's sitting idle. At least not from this issue :)

To restore the file, simply rename the file back.

Edited by QuasiZ, 23 February 2017 - 01:03 PM.

  • Abobader, Rominator and ParcelRot like this

#18 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 153470 posts
  • Local time: 05:46 PM

Posted 23 February 2017 - 01:01 PM

Interesting, thanks for the investigation. For those who might not read that whole thing, just to recap:

 

https://bug623317.bu....cgi?id=1318839

 

Thanks.



#19 daedalus OFFLINE  

daedalus

    Advanced Member

  • Members
  • 1320 posts
  • Local time: 11:46 PM

Posted 23 February 2017 - 02:44 PM

just tried it and can confirm that QuasiZ is right


Edited by daedalus, 23 February 2017 - 02:44 PM.

  • QuasiZ likes this

#20 RedStripe OFFLINE  

RedStripe

    Advanced Member

  • Members
  • 210 posts
  • Local time: 03:46 PM

Posted 24 February 2017 - 12:36 AM

Appears to have worked. Thx QuasiZ.


Edited by RedStripe, 24 February 2017 - 12:37 AM.

  • QuasiZ likes this





Also tagged with one or more of these keywords: CPU, usage, firefox, webclient, cpu

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users