[FIXr]Memory leak in nsDOMUIEvent::GetClientPoint

RESOLVED FIXED in mozilla1.8beta3

Status

()

Core
DOM: Events
P1
normal
RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: bz, Assigned: bz)

Tracking

({memory-leak})

Trunk
mozilla1.8beta3
x86
Linux
memory-leak
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

We're assigning a raw addrefed ptr into an nsCOMPtr...
Created attachment 184897 [details] [diff] [review]
Fix

docWidget is an nsCOMPtr and GetParent() returns a raw addrefed pointer...
Attachment #184897 - Flags: superreview?(rocallahan)
Attachment #184897 - Flags: review?(rocallahan)
Keywords: mlk
Priority: -- → P1
Summary: Memory leak in nsDOMUIEvent::GetClientPoint → [FIX]Memory leak in nsDOMUIEvent::GetClientPoint
Target Milestone: --- → mozilla1.8beta3
file a bug about converting nsIWidget::GetParent to return already_AddRefed?
Attachment #184897 - Flags: superreview?(roc)
Attachment #184897 - Flags: superreview+
Attachment #184897 - Flags: review?(roc)
Attachment #184897 - Flags: review+
That's bug 227489.

The problem is that it requires either manual inspection of all GetParent calls
(and we have lots of those for frames and content nodes that would need to be
filtered out) or changing the method name, test-compiling on all platforms to
catch all users and fix them up as needed, then changing it back....
Comment on attachment 184897 [details] [diff] [review]
Fix

Requesting 1.8b3 approval for simple leak fix.
Attachment #184897 - Flags: approval1.8b3?
Summary: [FIX]Memory leak in nsDOMUIEvent::GetClientPoint → [FIXr]Memory leak in nsDOMUIEvent::GetClientPoint
Comment on attachment 184897 [details] [diff] [review]
Fix

a=shaver
Attachment #184897 - Flags: approval1.8b3? → approval1.8b3+
Fixed for 1.8b3.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.