Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

high cpu usage, not many tabs open (less than 20)

  • 1 回覆
  • 1 有這個問題
  • 2 次檢視
  • 最近回覆由 quartz

more options

this seems to have only happened with a recent update

after a few hours open, the laptop's fan starts making noises. previous to a recent re start, I was getting about 50% (exactly) cpu usage after a few hours use (this has been for the past 2 or 3 weeks - 50% cpu use after a few hours of browser open, for 2-3 weeks). yesterday I restarted, process explorer is now showing 80% (80) cpu usage. Task manager shows my cpu almost maxed.

something's.....changed in the memory management or something. there has been a software change. noticeable step change

about....3 weeks ago till yesterday, 50% cpu use after Ff open for a few hours. today, cpu usage is now 80% after a few hours of brower open

I'm on 86.0.1, W7 64bit

this seems to have only happened with a recent update after a few hours open, the laptop's fan starts making noises. previous to a recent re start, I was getting about 50% (exactly) cpu usage after a few hours use (this has been for the past 2 or 3 weeks - 50% cpu use after a few hours of browser open, for 2-3 weeks). yesterday I restarted, process explorer is now showing 80% (80) cpu usage. Task manager shows my cpu almost maxed. something's.....changed in the memory management or something. there has been a software change. noticeable step change about....3 weeks ago till yesterday, 50% cpu use after Ff open for a few hours. today, cpu usage is now 80% after a few hours of brower open I'm on 86.0.1, W7 64bit

所有回覆 (1)

more options

( apparently I can't edit )

I can post a screenshot of process explorer. I have about 10 firefox processes listed right now. it's just one of them which has the 80% cpu. I guess I could kill the process with the 80% and see what happens