This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

Firefox using 50%+ of the CPU when it is inactive & only stops when I close & reopen it; then it starts it again after it is loaded for a while.

  • 3 àwọn èsì
  • 88 ní àwọn ìṣòro yìí
  • 15 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ Borne

more options

With Firefox loaded but sitting inactive for a period, it starts to use 50%+ of the CPU (per Windows Task Manager). This slows down everything even though there is nothing (overtly) going on with Firefox. If I close & reopen it, it is OK for a while, and then it starts again.

== In the past week, but I know of no specific event out of the usage ordinary.

With Firefox loaded but sitting inactive for a period, it starts to use 50%+ of the CPU (per Windows Task Manager). This slows down everything even though there is nothing (overtly) going on with Firefox. If I close & reopen it, it is OK for a while, and then it starts again. == In the past week, but I know of no specific event out of the usage ordinary.

Ọ̀nà àbáyọ tí a yàn

All Replies (3)

more options

Ọ̀nà àbáyọ Tí a Yàn

more options

I found the reason being the company web filter blocking one of my plugins. To test it you look for a plugin that is not working right and uninstalling it.

more options

Thank you for the link "AnonymousUser"... but the link no longer works.

I have been having this same issue for months now. It seems like at random times FF just jumps up to 50% CPU usage and basically freezes (very slow), and I have to restart it.

Sometimes when restarting FF it still does it, so I have to restart again.