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

Firefox uses Too Much RAM Tried Everything

  • 3 replies
  • 6 have this problem
  • 1 view
  • Last reply by philipp

more options

Per my task manager it's using 1.8GB of RAM. No themes installed and only extension is EVERNOTE and ADBlock. I've uninstalled multiple times. The RAM uses is out of control. I use Chrome, which has about 15 extensions, and it only uses 80MB of memory. Unfortunately Chrome is also very unstable so I can't use it on all websites. Thus I switch to FF but have to constantly close and re-open because it freezes so much.

My computer is new Zenbook with 8GB of memory and bottomless pit of HD. What can I do to fix this or is this just how FF is now?

Per my task manager it's using 1.8GB of RAM. No themes installed and only extension is EVERNOTE and ADBlock. I've uninstalled multiple times. The RAM uses is out of control. I use Chrome, which has about 15 extensions, and it only uses 80MB of memory. Unfortunately Chrome is also very unstable so I can't use it on all websites. Thus I switch to FF but have to constantly close and re-open because it freezes so much. My computer is new Zenbook with 8GB of memory and bottomless pit of HD. What can I do to fix this or is this just how FF is now?

All Replies (3)

more options

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram Firefox uses too much memory (RAM) - How to fix This article describes how to make Firefox use less memory to make it run faster and prevent crashes.

more options

Me too. And all the standard scripted link responses that I have already been through and tried multiple times don't help. But that's the answer you will get. It is either your fault or your extensions or here is a generic link that won't help that you have already read and tried.

more options

if you think you're seeing a memory leak bug, then it would be helpful if you can come up with data from about:memory obtained while the issue is happening - otherwise it's just a shot in the dark on our side and not much more than standard troubleshooting guides can be recommended...

http://dblohm7.ca/blog/2014/08/14/diffusion-of-responsibility/