為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox taking up about 900 MB of my RAM

  • 3 回覆
  • 85 有這個問題
  • 1 次檢視
  • 最近回覆由 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?

由 Sorcus 於 修改

所有回覆 (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.

由 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.