This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

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.

Learn More

Since the latest update (to 44.0, on win7), FF has been consuming nearly every available clock cycle - 60%-70% on my 6-core, 3.5GHz machine. Why?!??

  • 1 reply
  • 1 has this problem
  • 2 views
  • Last reply by FredMcD

more options

Since the latest update (to 44.0, on win7), FF has been keeping my cpu "pegged" (eating 60%-70% on my 6 core, 3.5GHz machine. IMO, this should *never* happen and is at least, at *some* level, a major regression. I do keep many window/tabs open but, it's never been this bad before. This is while no videos are playing (though I expect there's plenty of javascript running "quietly" on many pages, as is the way of the web these days). Is this a "known issue", is it being addressed (hopefully) ?

Since the latest update (to 44.0, on win7), FF has been keeping my cpu "pegged" (eating 60%-70% on my 6 core, 3.5GHz machine. IMO, this should *never* happen and is at least, at *some* level, a major regression. I do keep many window/tabs open but, it's never been this bad before. This is while no videos are playing (though I expect there's plenty of javascript running "quietly" on many pages, as is the way of the web these days). Is this a "known issue", is it being addressed (hopefully) ?

All Replies (1)

more options