Firefox goes to 99% CPU usage on Washingtonpost.com site (and others)
I am using Firefox 7 with Windows XP. When I connect to washingtonpost.com the CPU usage almost immediately stars going up until it reaches 99% after a few seconds and stays there. It often makes it impossible to switch to any other site without completely closing Firefox using "End Process" in Windows Task Manager.
Similar problem affects some other sites but since I have used washingtonpost.com for years as one of my primary news sources without any problems, does anyone know why this has only recently become a problem? I am having far more problems with Firefox recently than several years ago when it worked fine. Very frustrating.
I have tried clearing the cache/cookies etc. and it makes no difference.
Any suggestions?
選ばれた解決策
Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
- Don't make any changes on the Safe mode start window.
- https://support.mozilla.com/kb/Safe+Mode
You can also try to disable plugins (e.g. Flash) to see if that helps to isolate the problem.
この回答をすべて読む 👍 0すべての返信 (3)
Hi Geneva1-
Is this a problem exclusive to Firefox, or does it also happen in other browsers? Clearing the cookies and the cache are definitely the right first steps. I've found another Support article that details connection issues:
Firefox can't load websites but other browsers can
Hope that helps.
選ばれた解決策
Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
- Don't make any changes on the Safe mode start window.
- https://support.mozilla.com/kb/Safe+Mode
You can also try to disable plugins (e.g. Flash) to see if that helps to isolate the problem.
Just for info, I upgraded to Firefox 8 today and since then the high CPU usage problem mentioned in my original post seems to be corrected. Hope it lasts. Thanks for the other suggestions.