12 May 2011 19:39
Re: Firefox fat on Javascript?
Boris Zbarsky <bzbarsky <at> mit.edu>
2011-05-12 17:39:59 GMT
2011-05-12 17:39:59 GMT
On 5/12/11 11:52 AM, mfwitten <at> gmail.com wrote: > The data from about:memory for each firefox instance follows OK, so the gmail and vimperator ones have a much larger JS gc heap. That's actual JS objects that are in use by whatever JS code is running, and is consistent with the gmail and vimperator JS just creating a bunch of objects and holding on to them. The vimperator instance also has a bunch more images being used than the other two instances, and a _lot_ more layout datastructures. That's a little odd and may indicate leaks in either vimperator itself or Gecko in cases that vimperator tickles. If you start a browser with vimperator showing nothing but about:blank and do the same without vimperator (just use clean profiles for both, with one having vimperator installed), how do the about:memory outputs compare? Also, if you are willing to try a nightly build that would give much more readable and useful about:memory output; since the plan is to run against a clean profile anyway it won't get in the way of your other builds. > For dubious reasons, Mailman munged the Message-ID of my last email, This may have something to do with the fact that I'm reading this group and replying over NNTP, not e-mail. > If you add such munging to the fact that a user must subscribe to each > mailing list before posting(Continue reading)
RSS Feed