Closed
Bug 44665
Opened 24 years ago
Closed 24 years ago
leak of xptiInterfaceInfo from CallQueryInterfaceOnProxy
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: dbaron, Assigned: dougt)
Details
(Keywords: memory-leak, Whiteboard: [tind-mlk])
Attachments
(2 files)
446.74 KB,
text/html
|
Details | |
970 bytes,
patch
|
Details | Diff | Splinter Review |
I believe that nsProxyEventClass::CallQueryInterfaceOnProxy leaks the xptiInterfaceInfo returned to it from iim->GetInfoForName. I'm not sure if this leak is in all cases (or if in some cases something else takes over the reference). However, looking through a massive refcount balance tree that I will attach, it looks like this is responsible for leaks.
Reporter | ||
Comment 1•24 years ago
|
||
Reporter | ||
Comment 2•24 years ago
|
||
I accidentally attached that as HTML. I'm not going to waste another 450K of bugzilla disk space attaching it as text. It can be read easily in View-Source.
Reporter | ||
Comment 3•24 years ago
|
||
Assignee | ||
Comment 4•24 years ago
|
||
r=dougt. if you need me to check it in, let me know.
Assignee | ||
Comment 5•24 years ago
|
||
patch checked in
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Setting QA Contact to dbaron@fas.harvard.edu. David, can you verify when 2000-07-07 build is available later today? Thanks!
QA Contact: leger → dbaron
Reporter | ||
Comment 7•24 years ago
|
||
Marking as verified. Tinderbox leak stats dropped from 2 objects/5 refs to 2 objects / 2 refs when this was checked in. I suspect the other 2 refs may be owned by something else leaked, rather than leaked themselves, but it's worth checking. However, this leak is fixed.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•