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

Le thread ibilondoloziwe. Nceda ubuze umbuzo omtsha ukuba ufuna uncedo.

FF 95.0.2 (64-bit) started to "eat" memory / CPU till it gets dead

  • 4 iimpendulo
  • 1 inayo le ngxaki
  • 6 views
  • Impendulo yokugqibela ngu cor-el

Pilot Pirx
Pilot Pirx
more options

Good day! Things were fine for years till the problem with my FF (95.0.2 (64-bit), Windows 7 64 bit) started ~two days ago. As it started it persists every time I try to us the FF. Because of this new non-disappearing problem I had to move to Chrome instead.

As soon as my FF is opened and even when it has only one tab with no activity inside, its memory usage starts to grow rapidly and in a matter of minutes comes from ~900MB to ~6GB+ with the CPU usage "balancing" between ~25-45%. If I browse the used memory value grows a bit faster.

Along with that: - When the FF memory usage comes to ~85% of my memory, the FF browsing fails showing symptoms similar to a network issue (the network at the time is fine). - When the FF is closed, its processes are left along with their memory utilization keeping the same high rate till the FF processes are killed manually. - No add-ons / extensions or anything else were installed for months.

Please, assist in solving this sudden problem.

Good day! Things were fine for years till the problem with my FF (95.0.2 (64-bit), Windows 7 64 bit) started ~two days ago. As it started it persists every time I try to us the FF. Because of this new non-disappearing problem I had to move to Chrome instead. As soon as my FF is opened and even when it has only one tab with no activity inside, its memory usage starts to grow rapidly and in a matter of minutes comes from ~900MB to ~6GB+ with the CPU usage "balancing" between ~25-45%. If I browse the used memory value grows a bit faster. Along with that: - When the FF memory usage comes to ~85% of my memory, the FF browsing fails showing symptoms similar to a network issue (the network at the time is fine). - When the FF is closed, its processes are left along with their memory utilization keeping the same high rate till the FF processes are killed manually. - No add-ons / extensions or anything else were installed for months. Please, assist in solving this sudden problem.
Iqhotyoshelwe imifanekiso ekwisikrini

All Replies (4)

Pilot Pirx
Pilot Pirx Umnini wombuzo
more options

Comments about the screenshots.

  1. 1 - FF starts
  2. 2-#4 - FF memory usage grows / CPU usage is 25-45%
  3. 5 - FF is closed, but its processes are still there (till killed manually) and still eating lots of memory (~5+ GB).

Screenshots were taken with the time interval of ~2 minutes between each one.

FredMcD
FredMcD
more options

Start Firefox using Troubleshoot(Safe) Mode {web link}

A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?


https://support.mozilla.org/kb/Firefox+is+already+running+but+is+not+responding

https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram

https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

FredMcD
FredMcD
more options

Pilot Pirx said
- When the FF is closed, its processes are left along with their memory utilization keeping the same high rate till the FF processes are killed manually.

Are you closing the browser like this; Windows: Menu > File > Exit Mac: Menu > Firefox > Quit Firefox Linux: Menu > File > Quit

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

You can check the Firefox Task Manager (about:performance) and about:memory and about:processes pages.