Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Avatar for Username

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

High cpu usage of fifefox dev edition

  • 1 răspuns
  • 1 are această problemă
  • 17 vizualizări
  • Ultimul răspuns de 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.
Capturi de ecran atașate

Toate răspunsurile (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.