Steps to reproduce ------------------ * set firefox start page to "blank page" * quit firefox * set up leak logging (XPCOM_MEM_LEAK_LOG, leak-gauge setup, etc) * start firefox * press ^T (new tab) * quit firefox Results ------- Two nsHTMLDocument objects (amongst others) leaked according to XPCOM_MEM_LEAK_LOG. leak-gauge output: Leaked 2 out of 9 DOM Windows Leaked 29 out of 40 documents Leaked 0 out of 4 docshells
Does it still happen if you move aside the safe browsing JS components (nsSafeBrowsing*, nsUrlClassifier*)?
No leaks if those are moved aside: Leaked 0 out of 9 DOM Windows Leaked 0 out of 40 documents Leaked 0 out of 4 docshells
This is making any leak debugging very hard since it's very easy to run into this leak which swamps any other leaks.
Jonas, Brendan is supposedly working on this in bug 383269.
The checkin for bug 383269 appears to have fixed this particular leak.
Still fixed after the second patch there, right?
verified fixed using Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9b3pre) Gecko/2008010710 Minefield/3.0b3pre nsStringStats => mAllocCount: 16225 => mReallocCount: 3692 => mFreeCount: 16225 => mShareCount: 15617 => mAdoptCount: 2037 => mAdoptFreeCount: 2037 no leak -> Verified fixed