Created attachment 304225 [details] leak log Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b4pre) Gecko/2008021514 Firefox/3.0b4pre Steps to reproduce: New Firefox Profile - Install Wave https://labs.mozilla.com/forum/index.php/topic,393.0.html - (You need to have account to sign in into wave) - Go into the Wave Preferences -> Data -> Sync Now - Close Firefox during this Process --> Leak nsStringStats => mAllocCount: 37413 => mReallocCount: 4908 => mFreeCount: 36548 -- LEAKED 865 !!! => mShareCount: 32381 => mAdoptCount: 3060 => mAdoptFreeCount: 3057 -- LEAKED 3 !!! 0 TOTAL 26 228008 895476 7277 ( 2359.40 +/- 2125.38) 2515178 3484 ( 3042.13 +/- 4560.78) might be related to Bug 412774, will retest after the patch form bug 412774 lands.
Summary: Firefox leak on Exit during Wave Synchronization → Firefox leak on Exit during Weave Synchronization
The root leak for nsLayoutStatics here is the nsXMLHttpRequest. I wonder if this is due to network keeping it alive for too long.
Summary: Firefox leak on Exit during Weave Synchronization → Firefox leak nsXMLHttpRequest on Exit during Weave Synchronization
Assignee: nobody → jonas
Flags: blocking1.9? → blocking1.9+
Priority: -- → P3
Flags: tracking1.9+ → wanted-next+
weave is no longer used, right?
Severity: normal → minor
I would guess it's replaced with Firefox Sync? (In general it's probably better if you ask the reporter if the bug is still reproducible in a recent version of Firefox. They are more likely to know what the bug is about and how to reproduce it.)
I'm no longer working on this.
Assignee: jonas → nobody
Leaving this open doesn't seem useful to me. If Tomcat sees leaks with Synch he can file a new bug. :)
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.