Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i 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.

Læs mere

why isn't firefox freeing memory when a page is closed?

  • 1 svar
  • 3 har dette problem
  • 6 visninger
  • Seneste svar af bygabyga

more options

I just read that in the next version (54), firefox will be using up to four separate processes, and that that would save memory. I think my version may be doing so since 53, since it does no longer appear to keep session cookies for windows/tabs shut down. What I do NOT understand is why firefox does never free memory. I have to quit it for it free memory, even for closed tabs/windows. The free memory method provided by some plugins does not help. This ia a major issue with firefox, for me the worst one. :(

I just read that in the next version (54), firefox will be using up to four separate processes, and that that would save memory. I think my version may be doing so since 53, since it does no longer appear to keep session cookies for windows/tabs shut down. What I do NOT understand is why firefox does never free memory. I have to quit it for it free memory, even for closed tabs/windows. The free memory method provided by some plugins does not help. This ia a major issue with firefox, for me the worst one. :(

Alle svar (1)

more options

To restore it immediately?

Is your computer running out of memory?

Have you tried to fill it with other programs? Does Firefox unload then?

You could have a look at about:memory