Created attachment 300683 [details] leak log Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9b3pre) Gecko/2008013108 Firefox/3.0b3pre Steps to reproduce: -> new profile -> install the QA Extension -> Restart Firefox to enable the extension -> When Firefox was restarted click on the small icon icon in the status br -> Close/Cancel the Extension Setup Window (this has no affect to the leak if you set the extension up or close this window) -> In the QA Extension Window, click on "Chat" -> Click "Join irc now" -> You get connected to IRC -> After you see the QA channel, quit the IRC Client, you get a warning window and the chat window closes -> Close all QA Extension Windows -> Quit Firefox --> Leak nsDOMNodeAllocator leaked 5320 bytes nsStringStats => mAllocCount: 59257 => mReallocCount: 5603 => mFreeCount: 58369 -- LEAKED 888 !!! => mShareCount: 50017 => mAdoptCount: 3586 => mAdoptFreeCount: 3584 -- LEAKED 2 !!! 0 TOTAL 24 269739 1365470 7860 ( 3537.55 +/- 3288.99) 3956683 4005 ( 3542.27 +/- 5672.07) This might be related to Bug 412207, but the difference in this bug is, that i have closed before Firefox shutdown all QA Extension Windows and also have disconnected from Chat
So does the leak happen only if you've been connected to chatzilla at some point? Or can you reproduce without connecting somehow?
Created attachment 300727 [details] leak log2 (In reply to comment #1) > So does the leak happen only if you've been connected to chatzilla at some > point? Or can you reproduce without connecting somehow? > When i click on this Join IRC button, it starts a preconfigured chatzilla with the #qa channel. I get only a leak report when i was before connected to irc via this way. It makes also no difference if i disconnect chatzilla before i close the other windows.It get also a leak report.
But it doesn't leak if you never press the "Join irc now" button?
Depends on: 412207
Not a blocker, but would be very nice to have fixed since we're promoting this to the QA community. If you can get it to leak more than @ nsGlobalWindows please renominate
That should be If you can get it to leak more than _2_ nsGlobalWindows please renominate
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.