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.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

memory/CPU glutton

  • 2 replies
  • 2 have this problem
  • 2 views
  • Last reply by kuopiofi

kuopiofi
kuopiofi
more options

Right after chancing to Firefox 33.0 CPU use jumped insanely compared to 32 or any earlier. Even when I'm not opening anything or there's no active loading CPU use doesn't go below 50% use, when opening pages it takes easily double compared to earlier versions. Pages load slower and rolling them down is un-even.

Basically this version needs some serious work to reduce the load it puts on the memory/CPU, no amount of new options/safety justifies this amount of waste. KK

Right after chancing to Firefox 33.0 CPU use jumped insanely compared to 32 or any earlier. Even when I'm not opening anything or there's no active loading CPU use doesn't go below 50% use, when opening pages it takes easily double compared to earlier versions. Pages load slower and rolling them down is un-even. Basically this version needs some serious work to reduce the load it puts on the memory/CPU, no amount of new options/safety justifies this amount of waste. KK

All Replies (2)

kuopiofi
kuopiofi Question owner
more options

Went back to 32.3, CPU use went down to half, memory usage the same. Exactly what did you add to it to explain/justify that much memory/CPU need?

Tell me when you've fixed 33's massive glutting and I'll use it, this version isn't worth second look.

kuopiofi
kuopiofi Question owner
more options

From what I've seen/heard, Add-ons seem to be the problem, but considering that I use them for a reason...

I hope the next version fixes the discrepancy in FF 33, I'd *like* to use newest version of Firefox.