Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox 3.6.13 has a terrible memory leak

  • 3 antwoorden
  • 136 hebben dit probleem
  • 21 weergaven
  • Laatste antwoord van hansfn

plnelson
plnelson
more options

When I first start up Firefox it consumes < 100MB. After a few hours of browsing and other work it's over a gig. If I leave it up all day it's almost 2 gig - and my PC has only 2GB, which means everything starts paging like crazy. The only way to release it is to shut down all instances of the firefox.exe process. And when you do that it takes a long time because firefox has to release all that memory back to the system.

People are complaining about this all over the web and some people say "it's not firefox, it's the add-ons" but that's a cop-out because it's the firefox.exe process that's taking the memory. This means firefox provides the sandbox for the add-ons to run in so it can control their resource allocations.

When I first start up Firefox it consumes < 100MB. After a few hours of browsing and other work it's over a gig. If I leave it up all day it's almost 2 gig - and my PC has only 2GB, which means everything starts paging like crazy. The only way to release it is to shut down all instances of the firefox.exe process. And when you do that it takes a long time because firefox has to release all that memory back to the system. People are complaining about this all over the web and some people say "it's not firefox, it's the add-ons" but that's a cop-out because it's the firefox.exe process that's taking the memory. This means firefox provides the sandbox for the add-ons to run in so it can control their resource allocations.

Alle antwoorden (3)

hansfn
hansfn
more options

I have also noticed this memory leak. To be sure it wasn't my extensions, I launched Firefox with an profile with no extension. The memory leak was still very much present.

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

Did you check that there weren't any extensions installed in the new profile?

Plugins also can cause issues like that, so you can check that as well.

hansfn
hansfn
more options

Yes, I double-checked.

I did some testing:

1) Launching Firefox - 36 MB 2) Opening some random sites in 3-4 tabs and moving around on the sites (for an hour) - 168 MB 3) Closing all tabs, just leaving one empty tab - down to 116 MB, but staying there.

This is on Windows XP.