Memory leak testing needed on trunk builds (17:05 -0700)

Many of the leak regressions that resulted from the cycle collector landing have now been fixed, but the trunk still seems to be leaking more memory than it did six months ago. I've noticed this because I've been doing most of my browsing with leak logging, and looking at the resulting logs. However, I haven't had the time to simplify testcases for all the problems I'm seeing: that's sometimes a lot of work, and sometimes I can't figure out what I did on a page that would have caused it to leak (such that I see the leak again).

If you want Firefox 3 to leak less than Firefox 2, please help finding memory leaks. What's most useful right now is this:

1. Download the leak-gauge script (available in a perl version for those who have perl installed, or a slightly harder to use HTML + Javascript version for those who don't have perl).
2. Do your Web browsing using a Firefox trunk build with the environment variables set as described in the leak-gauge script, and then when you exit Firefox, run the leak-gauge script on the resulting log.
3. If you see leaks, figure out what caused them, and file good memory leak bugs in Bugzilla. (If you run into other bugs in the trunk builds, please file them too.)