Closed
Bug 130904
Opened 24 years ago
Closed 24 years ago
Leaks in nsHTMLCSSUtils::GetDefaultViewCSS()
Categories
(Core :: DOM: Editor, defect, P3)
Core
DOM: Editor
Tracking
()
VERIFIED
FIXED
mozilla1.0
People
(Reporter: glazou, Assigned: glazou)
Details
(Keywords: memory-leak, Whiteboard: fix in hand, need sr=)
Attachments
(1 file)
|
1.51 KB,
patch
|
peterv
:
review+
kinmoz
:
superreview+
asa
:
approval+
|
Details | Diff | Splinter Review |
We have leaks in nsHTMLCSSUtils::GetDefaultViewCSS() and should use nsCOMPtr's
there to easily solve the problem. My fault, even if I copied a large portion
of this code from another place in the source, that was fixed by someone else
in the meantime.
| Assignee | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
Comment on attachment 74082 [details] [diff] [review]
patch v1.0
r=peterv.
Attachment #74082 -
Flags: review+
| Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Whiteboard: fix in hand, need sr=
Target Milestone: --- → mozilla1.0
Comment on attachment 74082 [details] [diff] [review]
patch v1.0
sr=kin@netscape.com
- abstractView->QueryInterface(NS_GET_IID(nsIDOMViewCSS),
- (void **) aViewCSS);
+ CallQueryInterface(abstractView, aViewCSS);
return NS_OK;
Do we want to do a "return CallQueryInterface( ... )" , just in case the QI
fails? or does the caller check aViewCSS for NULL?
Attachment #74082 -
Flags: superreview+
| Assignee | ||
Comment 4•24 years ago
|
||
peterv had same question ; the caller always checks for null.
Comment 5•24 years ago
|
||
Comment on attachment 74082 [details] [diff] [review]
patch v1.0
a=asa (on behalf of drivers) for checkin to the 1.0 trunk
Attachment #74082 -
Flags: approval+
| Assignee | ||
Comment 6•24 years ago
|
||
checked in (trunk)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•