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.

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 takes up 2.6 million RAM after just an hour...

  • 1 resposta
  • 2 have this problem
  • 10 views
  • Last reply by kiyoteru

more options

Hi,

I've had a problem for about a year now where Firefox takes up too much physical memory. Recently it's been getting so bad that my RAM (6GB) usage is at 95% or higher and the freezing and lagging from Firefox gets so bad that I can't even close the program properly...

I heard recent news that an add-on extension I had was to blame for this, and now that I've gotten rid of it, it should be better, right? Well, it isn't; and I even looked at my about:memory.

As it turns out: vsize, resident, private, and heap-mapped are taking up over 1000MB each.

Any way I can reduce this?

notes: I've already tried "Minimize memory usage". the browser crashed for ten minutes to do this and it went down by about 200k, but it was momentary. It's still building memory.

Hi, I've had a problem for about a year now where Firefox takes up too much physical memory. Recently it's been getting so bad that my RAM (6GB) usage is at 95% or higher and the freezing and lagging from Firefox gets so bad that I can't even close the program properly... I heard recent news that an add-on extension I had was to blame for this, and now that I've gotten rid of it, it should be better, right? Well, it isn't; and I even looked at my about:memory. As it turns out: vsize, resident, private, and heap-mapped are taking up over 1000MB each. Any way I can reduce this? notes: I've already tried "Minimize memory usage". the browser crashed for ten minutes to do this and it went down by about 200k, but it was momentary. It's still building memory.

All Replies (1)

more options

PS: I tried uploading a picture, but big surprise, it didn't show. Here's the section from my about:memory scan a few hours ago.

http://i.gyazo.com/82f9f0bf37772a8c4e886b990b9595bd.png