Closed Bug 413888 Opened 17 years ago Closed 7 years ago

Firefox leaks nsXMLDocument with xmpp4moz Extension installed

Categories

(Core :: General, defect, P2)

x86
macOS
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: memory-leak)

Attachments

(2 files)

Attached file leak log
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2008012408 Firefox/3.0b3pre

Steps to reproduce:
- > New Profile
- > Install the xmpp4moz Extension
- > Restart Firefox to enable this extension
- > After the restart and this extension is enabled, quit firefox

- Leak

 0 TOTAL                                          28   225695   321761     7021 ( 1284.75 +/-  1600.57)  1066746     3342 ( 1456.58 +/-  2370.52)
Flags: blocking1.9?
Looks like we're leaking a single nsXMLDocument and a single nsXMLElement.

Tomcat, can you pound on this a bit harder and see if you can get it to leak any more documents or elements? Or even windows.
Summary: Firefox leaks with xmpp4moz Extension installed → Firefox leaks nsXMLDocument with xmpp4moz Extension installed
Jonas/Carsten move off blockign list if it is minor
Flags: blocking1.9? → blocking1.9+
Priority: -- → P2
Attached file new leak log
(In reply to comment #1)
> Looks like we're leaking a single nsXMLDocument and a single nsXMLElement.
> 
> Tomcat, can you pound on this a bit harder and see if you can get it to leak
> any more documents or elements? Or even windows.
> 

Hi Jonas, here is a new leak log with
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9b3pre) Gecko/2008012719 Firefox/3.0b3pre
Doesn't look like we're leaking any significant amount of data, i.e. the leak doesn't build up over time but is likely a shutdown leak.
Flags: wanted1.9+
Flags: blocking1.9-
Flags: blocking1.9+
Blocks: 416918
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: