19477 - Leaking nsSoftwareUpdateNameSet object

Status: RESOLVED FIXED

(SeaMonkey :: General, defect, P3)

Description

[Patrick C. Beard]

At the call site in the URL above, the call to nsSoftwareUpdate::GetInstance()
has already called AddRef(), and you are calling QueryInterface() which will also
call AddRef(). Therefore you're leaking a refcount.

Comment 1

[Daniel Veditz [:dveditz]]

That's not where the nsSoftwareUpdateNameSet leak comes from. the
SoftwareUpdate service doesn't keep a pointer to or AddRef the NameSet object,
it's just created and then passed to nsIScriptNameSetRegistry service. The
AddExternalNameSet() method on that service does the one and only AddRef on
that object, and never releases it.

Comment 2

[Jimmy Lee]

Not an XPInstall issue.  Changing QA Contact per Component change.

Comment 3

[vidur (gone)]

In an attempt to get my bug list in order again, marking all the bugs I have
currently as ASSIGNED.

Comment 4

[vidur (gone)]

Unfortunately the reference kept from the nsIScriptNameSetRegistry service can't
be released until the DOM becomes a full-fledged component. We aren't planning
on doing this till post-Beta 1. Marking M15.

Comment 5

[Johnny Stenback (:jst)]

This won't happend for M15, moving to M16.

Comment 6

[leger]

Updating QA Contact.

Comment 7

[Mike]

M16 has been out for a while now, these bugs target milestones need to be 
updated.

Comment 8

[Johnny Stenback (:jst)]

This bug has been marked "future" because the original netscape engineer
working on this is over-burdened. If you feel this is an error, that you or
another known resource will be working on this bug,or if it blocks your work
in some way -- please attach your concern to the bug for reconsideration.

Comment 9

[vidur (gone)]

Fixed with XPCDOM landing.