----- Original Message ----- > From: "Bas Schouten" <[email protected]> > To: [email protected] > Cc: "David Major" <[email protected]>, "Nathan Froyd" <[email protected]>, > "Firefox Dev" <[email protected]> > Sent: Tuesday, November 26, 2013 1:15:44 AM > Subject: Re: Reacting more strongly to low-memory situations in Firefox 25 > > > ----- Original Message ----- > > From: "Benjamin Smedberg" <[email protected]> > > To: [email protected], "Bas Schouten" <[email protected]>, > > "David Major" <[email protected]>, > > "Nathan Froyd" <[email protected]>, "Firefox Dev" > > <[email protected]> > > Sent: Monday, November 25, 2013 5:02:50 PM > > Subject: Reacting more strongly to low-memory situations in Firefox 25 > >
... > > > > == Graphics Solutions == > > > > The issues reported in bug 930797 at least appear to be related to HTML5 > > <video> rendering. The STR aren't precise, but it seems that we should > > try and understand and fix the issue reported by that user. Disabling > > hardware acceleration does not appear to help. > > ... > > For what it's worth, just to add some info to this, in my own experience on > my machines in most cases Firefox seems to climb to about 1.1-1.3 GB of > memory usage fairly quickly (i.e. < 2 days of keeping it open), and sort of > stabilize around that number. Usually when I do an about memory in this case > my memory reports about 500 MB+ in JS, a surprising amount (150 MB) in VRAM > usage for DrawTargets (this would be in our address space on the affected > intel machines), we should investigate the latter. This is usually with > about 20 tabs open. I've filed a bug for the latter part of this (the higher than expected DrawTarget memory usage), bug 944562. I'll look into it there. Although I don't think the number's high enough to cause a lot of trouble. I don't understand it and would like to. Best regards, Bas _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
