For the past several weeks I'm becoming increasingly aware of severe memory issues when using FF (currently FF30 32bit). No matter what I do, FF seems to keep allocating … (funda kabanzi)
For the past several weeks I'm becoming increasingly aware of severe memory issues when using FF (currently FF30 32bit). No matter what I do, FF seems to keep allocating more memory to the point where it starts having severe issues and slowdowns, eventually crashing when the used memory reaches about 2.4GB, according to Windows Task manager (I'm running Win7 64 on 8GB of RAM). Currently, the whole process got so bad that it only takes several hours for FF to crash. I don't even have to use FF for this to happen - if I simply leave it running for two hours, when I come back, it's process is already using a few hundred MB of memory more.
I've tried disabling all of the add-ons. I've tried disabling all of the plugins, including Flash (which is always udated to latest version). I've tried the safe mode. I've even tried a clean profile. Nothing really changes much - some of my add-ons might have some influence on how fast FF eats the RAM and they certainly have visible impact on how much memory is used from the start, but even without any add-ons, the memory footprint of FF still gets bigger and bigger over time just by regular browsing.
I've also tried both installing FF28 with clean profile into clean directory - again, the same behaviour was observed, although it used less memory by default and its memory footprint was getting bigger slower than with FF30. I've also tried current nightlies (FF33a1), both 32bit and 64bit, again with a clean profile, installed into a separate new folder. Again, didn't really solve anything.
I also have a second separate Windows 8 install on my PC, so I've tried FF30 in this install as well, however, it behaves exactly the same. FF does this even under my Linux installation, so I really doubt it has something to do with my Win install.
Note that I've also tried running current Pale Moon, and while its allocated memory grows much slower than with FF, it still grows over time unexplicably, and as Pale Moon is based on FF code, I'd say this suggests there's some kind of issue there.
Also note that I usually have quite a few tabs open (around 50 is my average - and no, I don't want to use less tabs, before someone suggests that, I think any browser on current hardware should be able to handle 50 tabs without much issues, and pretty much any other browser is), but the same behaviour was observed even with under 10 tabs. I also always disable the delayed tab loading, meaning that all of my tabs load at browser startup, not just after I click on them, so my starting memory footprint with all of my tabs and add-ons is around 1.4GB (1.1 in Pale Moon), which probably means I'm seeing this issue manifest faster than many other would. I'm fine with the memory it eats at startup and with the slower startup. I would even be fine with my browser taking up 2 gigs of RAM (I've got 8GB of RAM for a reason), as long as it doesn't keep on allocating more and more memory without it ever going back down, even when I close several tabs.
Finally, it might be interesting to note that the memory measurements at about:memory grow much slower than the allocated memory reported by Task manager - meaning that quite often, FF memory measurement says it's using 1395MB RAM, while in Windows Taks manager, the Firefox32 process is reported as already taking up e.g. 1.8-2.0GB of RAM, and around 1500MB RAM in FF can equal to 2.2-2.4GB in Task Manager (meaning it's pretty close to FF crashing). And the "Free memory" buttons in about:memory seem to have no effect on the allocated memory, reported in Task manager (even though they do have some minor effect on used memory reported by FF itself there).
I don't really expect much help, I think I've already tried pretty much everything there was to try and for the time being it seems to me using Pale Moon is my only option right now, as in it the memory issues are at least somehow manageable and not as annoying as in classic FF, but I still thought I might post this here, if perhaps only for someone to take notice.