This meta bug is for leaks QA found or hit while testing Firefox 3 with Litmus Testruns for Leaks
Leak Logs are stored on http://people.mozilla.com/~cbook/memleak/
tomcat, can you post a link to the test procedure you are using to generate the leak logs here? I'll help evangelize this to extension developers so they can join in on testing their extensions and helping to find core and extension problems.
So, there's http://wiki.mozilla.org/MozillaQualityAssurance:Home_Page:Firefox_3.0_TestPlan:Leaks:LeakTesting-How-To on how to check for leaks.
* This currently requires a complete build environment, which few extension devs and not even all Firefox devs will have handy.
* The leak logs don't seem too useful (unless I'm missing something in which case some reading help would be most welcome).
* Furthermore there are no hints as to what code patterns might lead to leaks (I thought the new cycle collector should've taken care of most of them).
* Finally: How do we know that these leaks are really to blame on particular code and don't rather have a common core issue (which XUL/JS code can't to much about at all)? I see especially many references to nsGlobalWindows...
A lot of these seem to leak two nsGlobalWindows. I'm fairly certain that those are still instances of bug 398219 (see bug 398219, comment 32). We'll probably file a new bug to really fix those instances of bug 398219.
changing subject of this bug since one focus of the leak testing is also on extensions and not only testcases from litmus.mozilla.org.
filed bug 422471 for memory leaks found in extensions by the amo-editors and/or extension devs/community
closing old meta bugs we aren't using anymore either because we don't need to or because we shipped the releases attached to these.