Created attachment 296612 [details] XPCOM_MEM_LEAK_LOG for session sayrer is trying to help me track down some leaks I'm having. Attached is the XPCOM mem leak log that I can reproduce consistently. Here are the steps I used to get these leaks: 1. XPCOM_MEM_LEAK_LOG=leaklog-emptyprof-2008011.log ./firefox -no-remote -P 2. Create new profile using profile manager 3. Start browser with new profile 4. Say no to "default browser" message 5. Select File->Quit 6. Say no to "Do you want to save tabs..." message 7. Frown at leak log
Attachment #296612 - Attachment filename: leakmebabybe-empty.log → leaklog-emptyprof-20080111.log
Created attachment 306596 [details] new leak log confirmed with the steps to reproduce from reed: nsStringStats => mAllocCount: 26119 => mReallocCount: 3759 => mFreeCount: 25535 -- LEAKED 584 !!! => mShareCount: 19452 => mAdoptCount: 1652 => mAdoptFreeCount: 1650 -- LEAKED 2 !!! 0 TOTAL 27 218363 365704 6775 ( 1150.93 +/- 1429.27) 1124449 3079 ( 1537.75 +/- 2513.11)
Flags: tracking1.9+ → wanted-next+
re-nominating for blocking since: I did some tests again and it seems that this leaks every time when the default browser question comes up. So its not only a leak when you create a profile
OS: Linux → All
I'd still say we have more important leaks to fix.
Summary: Leaks found when using new profile → Leaks when getting "default browser" dialog
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.