Avatar for Username

Претражи подршку

Избегните преваре подршке. Никада од вас нећемо тражити да зовете или шаљете поруке на број или да делите личне податке. Пријавите сумњиве радње преко „Пријавите злоупотребу” опције.

Сазнај више

Ова тема је архивирана. Питајте друго питање ако вам је потребна помоћ.

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 одговорa
  • 88 има овај проблем
  • 15 прегледа
  • Последњи одговор послао Borne

AnonymousUser
AnonymousUser
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.

Изабрано решење

Please see http://support.mozilla.com/en-US/forum/1/656957

Прочитајте овај одговор са објашњењем 👍 0

Сви одговори (3)

AnonymousUser
AnonymousUser Власник питања
more options

Одабрано решење

Please see http://support.mozilla.com/en-US/forum/1/656957

zal
zal
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.

Borne
Borne
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.