Linked by Thom Holwerda on Wed 27th Feb 2013 22:42 UTC
Thread beginning with comment 554032
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: there is nothing wrong with the hardware
by Alfman on Fri 1st Mar 2013 23:31
in reply to "RE[6]: there is nothing wrong with the hardware"
Fergy,
As a dev myself I'd feel it necessary to take out all the variables by turning off all the plugins and confirming the leak still exists. I'm not thrilled at running without adblock/ghostery/firebug for a week.
I'd be kind of surprised if they aren't already aware of the problem, so it's probably a matter of finding a similar bug and saying "me too".
RE[8]: there is nothing wrong with the hardware
by Fergy on Sat 2nd Mar 2013 13:14
in reply to "RE[7]: there is nothing wrong with the hardware"




Member since:
2006-04-10
As far as I can tell it's not related to what I'm doing, just a slow continuous leak of some sort that persists even after I close all but one tab.
about:memory doesn't look very meaningful to me, but right now with nothing but osnews open I see js-non-window at 80MB and js-main-runtime at 90MB. Everything else is much lower in comparison so a pure guess is that's it's a JS related leak. But for all I know it might be one of the plugins I've installed.
On my linux box it usually takes a week or two before firefox starts to crawl at a few gigs of ram. This happens regularly because the system is always on. On the windows side the computer is restarted every day, so although the memory usage climbs, it never becomes unusable.
I haven't tried chrome for comparison.
You can post your about:memory after you feel Firefox has slowed down after 2 weeks. Maybe in a bug to Mozilla or in the forums. Look up project snappy because they would be really interested.