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

Èròjà atẹ̀lélànà yii ni a ti fi pamọ́ fọ́jọ́ pípẹ́. Jọ̀wọ́ béèrè ìbéèrè titun bí o bá nílò ìrànwọ́.

FF not relasing memory, slowing PC OPs

  • 1 èsì
  • 1 ní ìṣòro yìí
  • 2 views
  • Èsì tí ó kẹ́hìn lọ́wọ́ Matt_G

N6JSX
N6JSX
more options

From V3.6.18 via WinXP to V9.X via Win7 using DSL/Cable - on multiple PC/NB's.... Running only three tabs, I've found that FF does not release unused/closed items memory - leading to my whole FF/PC "ALL" operations going super slow.

My solution is to go to WinTaskMngr/Processes and view FF mem-use. If mem-use is >250K the PC will start slowing down >1Meg and it is crawling! I highlight FF - right click and hit 'End Process' killing FF. Then restart FF via icon and all is FAST again! May not be the right way but it works and my speed is back to normal and Win does not care!

I do not do a normal FF exit as it hang up for ~10min. The FF page closes but if you try to restart right away it says FF is still running prohibiting a restart. The above method does not have any wait state in firing FF back up!!!

From V3.6.18 via WinXP to V9.X via Win7 using DSL/Cable - on multiple PC/NB's.... Running only three tabs, I've found that FF does not release unused/closed items memory - leading to my whole FF/PC "ALL" operations going super slow. My solution is to go to WinTaskMngr/Processes and view FF mem-use. If mem-use is >250K the PC will start slowing down >1Meg and it is crawling! I highlight FF - right click and hit 'End Process' killing FF. Then restart FF via icon and all is FAST again! May not be the right way but it works and my speed is back to normal and Win does not care! I do not do a normal FF exit as it hang up for ~10min. The FF page closes but if you try to restart right away it says FF is still running prohibiting a restart. The above method does not have any wait state in firing FF back up!!!

All Replies (1)

Matt_G
Matt_G
more options

Hi N6JSX,

Have you looked at the Knowledge Base article Firefox uses too much memory or CPU resources - How to fix or Firefox uses too much memory or CPU resources - How to fix? There is a lot of great information in there.

Hopefully this helps!