Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

High cpu usage of fifefox dev edition

  • 1 antwoord
  • 1 heeft dit probleem
  • 17 weergaven
  • Laatste antwoord van 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.
Gekoppelde schermafbeeldingen

Alle antwoorden (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.