My issue is, FF climbs up to 2.5GB of memory usage, then it dies. 100% repro.
My only add-ons are AB+, Reddit Enhancement Suite, and No Redirect. I am 99% sure this was happening before Noredirect, but I'll try disabling that as well. (Super useful though, wow!)
(GreaseMonkey is also installed, but I don't have any scripts loaded in it, disabling it anyway)
Of course if you run into the 32bit memory limit, I don't know if there is much FF can do about it! Right now I am at ~1,5800MB.
Actually this is sort of amusing, the memory usage counts up to 1590, then drops down to 1570, then counts up to 1591, drops to 1571, counts to 1592, drops to 1572, I am watching some stupid web app leak memory in real time.
(Maxed out at 1588 when I started typing, now maxing out at 1606, heh)
All of this is as reported in Windows Task Manager so numbers are wildly inaccurate I assume, still funny. (About:memory is showing the same thing happening!)
Ah the wonders of crappy JS programmers.
Edit: Haven't changed any websites or loaded any new tabs, now it is cycling up to 1630MB. :P
The performance of Firefox on Reddit is absolutely terrible. It regularly freezes my machine, at which point I do a global FF exit and restart / restore session so that it puts some tabs on "lazy load" state.
I wonder if the Reddit Enhancement Suite add-on is the culprit. The "Never Ending Reddit" infinite scrolling feature sounds like it could consume a lot of memory without releasing it. Unfortunately, if the Reddit add-on outlives any reddit.com tabs, it might inadvertently keep those JS objects alive in the background.
> Unfortunately, if the Reddit add-on outlives any reddit.com tabs, it might inadvertently keep those JS objects alive in the background.
With a 64bit memory address space, who cares?
OK so my page file does.
I think I've only given it 100GB or so to play around with, so, sure, if the 32GB of system ram I have available fills up, and all 100GB of my page file get used up, then I'll have to restart FF.
At ~5GB a day of usage, and lets round down for the sake of losses, that is about 20 days of up time before Firefox is denied malloc's by my OS.
Still not great, but a lot better than crashing twice a day!
Comments
My issue is, FF climbs up to 2.5GB of memory usage, then it dies. 100% repro.
My only add-ons are AB+, Reddit Enhancement Suite, and No Redirect. I am 99% sure this was happening before Noredirect, but I'll try disabling that as well. (Super useful though, wow!)
(GreaseMonkey is also installed, but I don't have any scripts loaded in it, disabling it anyway)
Of course if you run into the 32bit memory limit, I don't know if there is much FF can do about it! Right now I am at ~1,5800MB.
Actually this is sort of amusing, the memory usage counts up to 1590, then drops down to 1570, then counts up to 1591, drops to 1571, counts to 1592, drops to 1572, I am watching some stupid web app leak memory in real time.
(Maxed out at 1588 when I started typing, now maxing out at 1606, heh)
All of this is as reported in Windows Task Manager so numbers are wildly inaccurate I assume, still funny. (About:memory is showing the same thing happening!)
Ah the wonders of crappy JS programmers.
Edit: Haven't changed any websites or loaded any new tabs, now it is cycling up to 1630MB. :P
The performance of Firefox on Reddit is absolutely terrible. It regularly freezes my machine, at which point I do a global FF exit and restart / restore session so that it puts some tabs on "lazy load" state.
I wonder if the Reddit Enhancement Suite add-on is the culprit. The "Never Ending Reddit" infinite scrolling feature sounds like it could consume a lot of memory without releasing it. Unfortunately, if the Reddit add-on outlives any reddit.com tabs, it might inadvertently keep those JS objects alive in the background.
> Unfortunately, if the Reddit add-on outlives any reddit.com tabs, it might inadvertently keep those JS objects alive in the background.
With a 64bit memory address space, who cares?
OK so my page file does.
I think I've only given it 100GB or so to play around with, so, sure, if the 32GB of system ram I have available fills up, and all 100GB of my page file get used up, then I'll have to restart FF.
At ~5GB a day of usage, and lets round down for the sake of losses, that is about 20 days of up time before Firefox is denied malloc's by my OS.
Still not great, but a lot better than crashing twice a day!