3 ms·

I applaud the Mozilla team for its huge effort in squashing the FF memory leaks. That must have been such a huge pain to solve and it took many years. Well done

I applaud the Mozilla team for its huge effort in squashing the FF memory leaks. That must have been such a huge pain to solve and it took many years. Well done and congrats. That said, I really hope the authors of plugins like Firebug, Adblock Plus, and LastPass among many others will do their parts to get rid of bad memory leaks. Using OSX 10.7.4, I opened up FF 14.1 to about 325MB-350MB of memory. After downloading FF 15 and restarting, I saw no change in my memory consumption. Once I disabled the three I mentioned above, I was only then able to start FF around 250MB, still really high but better. I want Mozilla and Firefox to succeed as I really want there to be solid competition for Chrome. Please, add-on authors, do your parts too!

pilif 14y ago
By just starting Firefox and looking at the memory consumption, you are measuring exactly that: Consumption. Not leakage. Leaking implies a continuously increasing memory usage. By just opening, measuring and closing again, you don't even get a chance to measure an increase in consumption, so you can't say anything about leakage. Also, 100MB for Firebug, Adblock and LastPass doesn't seem that far off - especially Firebug is huge and has to do a lot of work, so I would expect that to require quite a bit of memory.
- technojunkie 14y ago
  Good point and I will continue to monitor the browser as I use it. Just in initial browsing, I'm still finding the memory consumption increasing at the same alarming rate it was before sadly. :( But you are correct that I need to give it some time to really measure correctly. That said, even with the 9 add-ons I'm using, I was hoping I could see a total memory usage on startup to be closer to 225MB.
  - mtgx 14y ago
    Also having the lowest memory consumption is not always the best indicator for how good a browser is. For example, I think Chrome uses more memory per tab than most other browsers, because of its individual sandboxing system. But that seems to be a pretty fair trade-off. Has Firefox started using sandboxing yet?
    - jeltz 14y ago
      Firefox only sandbox plugins like Flash, but they have plans for more sandboxing. No idea what the status is though.
    - technojunkie 14y ago
      Maybe you're right about lowest memory consumption, but what keeps me going back to Chrome is consistency in good performance and the fact that I can easily shut down one tab without having to restart the whole browser to reduce memory if that ever happens. All browsers do have memory leaks but the fact that FF's memory continually increases to the point where I have to restart the whole browser every day is mentally tiring. This is where Chrome just got it right.
      - robin_reala 14y ago
        FF's memory continually increases to the point where I have to restart the whole browser every day That’s really not the case any more.
        ralfn 14y ago
        This was fixed for extension-free firefox. Today this is fixed, for extensions as well. What was happening was that extensions had references to dom-nodes of a page, that prevented the page from being unloaded when you close the tab. Unless of course, the extendion author bothered to fix this from their side. Now, an extension has essentially "weak references" to dom nodes. (think: symlink)
        icarus127 14y ago
        I second this. On Ubuntu 12.04 Unity crashes after approximately 20 days of uptime and that's Almost the only time I restart Firefox. I regularly have a single session open for weeks.
      - technojunkie 14y ago
        That’s really not the case any more. So far in my testing and browsing, it is.
  - gareim 14y ago
    I'm using Firefox 17a1 on Linux and with 6 tabs open plus NoScript and Adblock, I'm getting about somewhere in the low 200s for mb of RAM used.
  - ubernostrum 14y ago
    If you want to know what it's using memory for, hit about:memory. This is also a useful way to start looking at a suspected leak: visit a page and hit about:memory to see what it's using, then close the tab and check about:memory again to see whether it's freeing everything.

pilif 14y ago

By just starting Firefox and looking at the memory consumption, you are measuring exactly that: Consumption. Not leakage. Leaking implies a continuously increasing memory usage. By just opening, measuring and closing again, you don't even get a chance to measure an increase in consumption, so you can't say anything about leakage. Also, 100MB for Firebug, Adblock and LastPass doesn't seem that far off - especially Firebug is huge and has to do a lot of work, so I would expect that to require quite a bit of memory.

technojunkie 14y ago
Good point and I will continue to monitor the browser as I use it. Just in initial browsing, I'm still finding the memory consumption increasing at the same alarming rate it was before sadly. :( But you are correct that I need to give it some time to really measure correctly. That said, even with the 9 add-ons I'm using, I was hoping I could see a total memory usage on startup to be closer to 225MB.
- mtgx 14y ago
  Also having the lowest memory consumption is not always the best indicator for how good a browser is. For example, I think Chrome uses more memory per tab than most other browsers, because of its individual sandboxing system. But that seems to be a pretty fair trade-off. Has Firefox started using sandboxing yet?
  - jeltz 14y ago
    Firefox only sandbox plugins like Flash, but they have plans for more sandboxing. No idea what the status is though.
  - technojunkie 14y ago
    Maybe you're right about lowest memory consumption, but what keeps me going back to Chrome is consistency in good performance and the fact that I can easily shut down one tab without having to restart the whole browser to reduce memory if that ever happens. All browsers do have memory leaks but the fact that FF's memory continually increases to the point where I have to restart the whole browser every day is mentally tiring. This is where Chrome just got it right.
    - robin_reala 14y ago
      FF's memory continually increases to the point where I have to restart the whole browser every day That’s really not the case any more.
      - ralfn 14y ago
        This was fixed for extension-free firefox. Today this is fixed, for extensions as well. What was happening was that extensions had references to dom-nodes of a page, that prevented the page from being unloaded when you close the tab. Unless of course, the extendion author bothered to fix this from their side. Now, an extension has essentially "weak references" to dom nodes. (think: symlink)
      - icarus127 14y ago
        I second this. On Ubuntu 12.04 Unity crashes after approximately 20 days of uptime and that's Almost the only time I restart Firefox. I regularly have a single session open for weeks.
    - technojunkie 14y ago
      That’s really not the case any more. So far in my testing and browsing, it is.
- gareim 14y ago
  I'm using Firefox 17a1 on Linux and with 6 tabs open plus NoScript and Adblock, I'm getting about somewhere in the low 200s for mb of RAM used.
- ubernostrum 14y ago
  If you want to know what it's using memory for, hit about:memory. This is also a useful way to start looking at a suspected leak: visit a page and hit about:memory to see what it's using, then close the tab and check about:memory again to see whether it's freeing everything.