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 taking up about 900 MB of my RAM

  • 3 replies
  • 85 have this problem
  • 3 views
  • Last reply by poetpriest

more options

I did check the other questions before posting this, but Firefox 4.0 taking up almost upwards of 900 MB of RAM suggests that there is a memory leak. With only 6 tabs open and none flash, this only suggests that there is a memory leak that is eating up my RAM for all its worth.

Also, to add to this is the fact that every minute it increases RAM usage by 4-5 mb. I just ran a test on it and I saw a Firefox 4.0 window with 5 active tabs using about 1.5 GB of my RAM single handedly. Being an ardent Firefox user for many years , this saddens me.

Is there any advice on this?

I did check the other questions before posting this, but Firefox 4.0 taking up almost upwards of 900 MB of RAM suggests that there is a memory leak. With only 6 tabs open and none flash, this only suggests that there is a memory leak that is eating up my RAM for all its worth. Also, to add to this is the fact that every minute it increases RAM usage by 4-5 mb. I just ran a test on it and I saw a Firefox 4.0 window with 5 active tabs using about 1.5 GB of my RAM single handedly. Being an ardent Firefox user for many years , this saddens me. Is there any advice on this?

Modified by Sorcus

All Replies (3)

more options

Possible Solution: I had the same occurring issue with my firefox too. I found that disabling the page file in windows fixed up my memory leak. It seems firefox stays in memory and takes space on your OS's pagefile, causing reports of doubled memory in the task manager.

more options

Thanks gosu, but it didn't work for me. So, its been 2 days and no one actually answers this. This is what is termed as irresponsible. This memory leak is a serious issue but the devs decide to keep mum.

Modified by Sorcus

more options

Well, no one works on memory leaks, that's why no one responds. They inevitably are hard to find, no one wants to work hard. They inevitably involves someone else's code, no one likes to clean up other people's messes. They inevitably make no splash as there is no great neato interface or feature offered, no one likes to work without getting their ego stroked.

This is the problem with a totally grassroots development construct. The hard necessary work rarely gets done.