I am using the latest version of Firefox, 32.0.1, on an HP Pavilion dv7-4141sa laptop computer, running Windows 8.1 Pro 64-bit. There should be more than enough power he… (xem thêm)
I am using the latest version of Firefox, 32.0.1, on an HP Pavilion dv7-4141sa laptop computer, running Windows 8.1 Pro 64-bit. There should be more than enough power here to run a browser without any problem, yet the computer is regularly being overloaded by the browser's resource usage.
I am currently measuring typical average CPU usage of 45% - with the browser minimised. That is to say, Firefox is not doing any browser jobs - it is not drawing on the screen - but it is using the most CPU of any process currently running. Why?
I am an ex-software engineer, and my understanding of current application development technology is limited, but I think I can say with some confidence that many techniques and software architectures exist that enable the suspension of program activity, or at least its reduction to a very low bare minimum, when the program is not actually carrying out its design function, which is in this case to draw pictures of website data on a screen.
There is a very serious problem here, one which means that I cannot run Firefox all the time, but have to kill it when I am not actively browsing, otherwise other applications cannot run to their full capacity. This is a great pity, because I have committed a lot of effort to making Firefox my primary web tool. It manages all my many bookmarks, contains my secure password manager (LastPass), manages my web security (via NoScript, AdBlock, and FlashBlock), just for a start.
Before any well-meaning moderators or other commenters start down the usual trail of "have you done this, tried that, disabled the other", I should point out that I have followed all the advice I can find, with no positive outcome. This computer is running a fresh installation of Windows, and a fresh installation of Firefox. At the moment I am running a new test Firefox profile.
The latest version of Adobe Flash, 188.8.131.52, is installed but disabled. When it is enabled and in use, Firefox's CPU usage seems high over longer periods, but overall there is little difference. It doesn't look as though the problem can be laid at Flash's door. A few other add-ins are installed, mainly those mentioned above, and Firefox is skinned with LavaFox v2-Green, but I have previously started from a clean installation, which has made little difference after an initial period during which things seemed to be better. Turning off or disabling various add-ons has made no discernible difference.
Just now I turned Flash on, and after a long period with Firefox minimised, Resource Monitor reported Firefox at 8% average CPU and FlashPlayerPlugin at 0.32%. While running a small video, RM reports FlashPlayerPlugin at about 45% and Firefox at 8%. After the video, Flash went back down to around 0.4%, and after a bit more browsing Firefox went to around 17% minimised. There seems little rhyme or reason here, except that Flash does not seem to be the culprit, although Firefox does seem to consume less when fewer tabs are actually active, as you might expect. I just refreshed more than a dozen tabs, and now Firefox is at 30%, but still not back up to the higher figures. Weird.
The CPU usage does vary a lot around the average, but 30% is still a lot for a program that shouldn't be doing anything above the minimum status maintenance, and still puts it at the top of my Top Process Monitor list. (Right now it's gone back up to 45%, without my using it in any way).
I have Telemetry turned on, so presumably Mozilla is recording some of the relevant data.
This is a very serious fault, which is more or less reproducible and which a lot of people seem to be experiencing. Probably more people have it than realise, because most users will not know anything other than that their computer slows down for some non-obvious reason; they may just think it's something to do with the computer itself, not knowing how to use the Resource Monitor and interpret the results.
Oddly, the problem does not seem to occur when running Firefox under Linux Mint 17, where the response is snappy and the CPU usage ostensibly low; I am going to look at this in more detail shortly.
I am not posting here for advice, but for information and as a form of bug report which hopefully other users will see. It will hopefully spare them a lot of effort and time in trying a lot of recommended "solutions" which will not work. The problem is inherent in the software, and can be solved only by Mozilla.
I am willing to supply any diagnostic data requested; as I said above, I have also turned on "Telemetry". However, I will not be trying out any more reinstallation/new-profile/add-on disable-enable-delete cycles unless I am asked to for very specific reasons. Please do not suggest courses of action which have already been mentioned elsewhere on this forum. I have tried them all.
The situation is very disappointing, but I have confidence that the Firefox developers will pin down the fault eventually and engineer a satisfactory solution that makes it viable to leave Firefox open all the time. Even with that restriction, it's still far better than the alternatives.