firefox is using 1-2% (or more) of the cpu when idle. is it normal?
been a user of ff since 0.9 version when ie6 pissed me off.
while using ff i noticed it's consatntly using 1-2% of my cpu even when the active tab is something static. it jumps when doing stuff but the baseline on my core 2 duo 6700 (2,66ghz) cpu is 1-2%.
http://i50.tinypic.com/1c8xg.jpg
same happens on my quad core nehalem. even with no tabs open i still get that constant noise activity. this is not a big deal on a desktop but on my laptop this for sure drains the battery as it keeps the cpu active.
later edit: so... opened a new window with no open tab and closed the first window... cpu at 1,5% mostly and quite stable at this value.
opened google home page, closed ff, open again so that there would not be any closed tabs in memory. basically ff started and opened one tab with google search page opened and doing nothing. the cpu was at 2% most fo the time with some seldom spikes to 5-10%.
this shows me that the (little) constant cpu usage is not realted to tabs opened, closed. it may be related to addons. however i remeber i opened ff with all addons disabled, no active tabs and still the cpu usage.
i'm not sure if this is the internal cleanup activity or activity realted to tabs being active, getting updates, playing music, getting emails... javascript activity.
there are cases when somone decide to make some funky snow-falling effect on one page, eating a lot of cpu. that would continue to peg the cpu even when the tab is tot the active one. this would be worse when i would minimize ff to do something else and i would still pay the price. i would expect that the inactive tabs would freeze completely or be allowed to get resources from time to time. the from time to time would be the model windows 8 uses for metro apps. the apps are open but when minimized they get suspended and from time to time the tiles would update.
my thoughts - when minimized ff should update from time to time like the win 8 tiles do and use the cpu as little as possbile - the active tab should get the fully required cpu esources but the hidden tabs should either get cycles from time to time or completly freeze
is it normal that firefox would use a little of the cpu when nothing is active?
later edit:
so... opened a new window with no open tab and closed the first window... cpu at 1,5% mostly and quite stable at this value.
opened google home page, closed ff, open again so that there would not be any closed tabs in memory. basically ff started and opened one tab with google search page opened and doing nothing. the cpu was at 2% most fo the time with some seldom spikes to 5-10%.
this shows me that the (little) constant cpu usage is not realted to tabs opened, closed. it may be related to addons. however i remeber i opened ff with all addons disabled, no active tabs and still the cpu usage.
Modificato da CosminNet il
Tutte le risposte (3)
edit: merged the content to original message
Modificato da CosminNet il
Create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
- https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles
- http://kb.mozillazine.org/Standard_diagnostic_-_Firefox#Profile_issues
If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.
i thank u for the response but don;t see how it relates to my findings. however i installed a clean ff 19, no addons, on a virtual box vm running win 2012 server. with google search page it was using ~0.1% of cpu (checked it using process explorer). the issue seems a lot less than my initial findings. this leads me to conclude that some of the plugins may be causing this. i can't think of a reasonable way to see which is the culprit, unless is start unistalling plugins and i do not want to do that.
i think that also plugins may be allowed to run once in a while, basically having the same run profile that i sugested initially. i would not trust the plugins much and would have a more restrictive policy on them.
ps: one can say it's not ff doing tha damage, it's the plugins. even if true the user will blame ff for any misbehavings.
Modificato da CosminNet il