Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

Támogatás keresése

Kerülje el a támogatási csalásokat. Sosem kérjük arra, hogy hívjon fel egy telefonszámot vagy osszon meg személyes információkat. Jelentse a gyanús tevékenységeket a „Visszaélés bejelentése” lehetőséggel.

További tudnivalók

A témacsoportot lezárták és archiválták. Tegyen fel új kérdést, ha segítségre van szüksége.

High cpu usage of fifefox dev edition

  • 1 válasz
  • 1 embernek van ilyen problémája
  • 17 megtekintés
  • Utolsó üzenet ettől: asdf2345

Yash
Yash
more options

When watching youtube or even doing a little task with only one tab the cpu usage from a specific firefox process goes upto 90%. And I have did everything that was given in the following troubleshoot method "https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources" but still the same result. I tried with troubleshoot mode on with disabling all extensions but the cpu usage was still high. I have also checked with firefox's own task manager tool but there wasn't a single process that was using full cpu. I'll be attaching all screenshots below.

When watching youtube or even doing a little task with only one tab the cpu usage from a specific firefox process goes upto 90%. And I have did everything that was given in the following troubleshoot method "https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources" but still the same result. I tried with troubleshoot mode on with disabling all extensions but the cpu usage was still high. I have also checked with firefox's own task manager tool but there wasn't a single process that was using full cpu. I'll be attaching all screenshots below.
Csatolt képernyőmentések

Összes válasz (1)

asdf2345
asdf2345
more options

I have this issue as well. I can close the process using task manager and that fixes the issue, but it pops up again later. No clue what's causing it. Might even be in stable by now.