Mem leak when preferred effect is set for drag and drop

RESOLVED FIXED in mozilla9



8 years ago
8 years ago


(Reporter: bbondy, Assigned: bbondy)



Windows 7
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [MemShrink])


(1 attachment)



8 years ago
Bug 296528 introduced a memory leak with the following code in nsClipboard.cpp:

>   nsresult loadResult = nsClipboard::GetNativeDataOffClipboard(
>       pIDataSource, 0, ::RegisterClipboardFormat(CFSTR_PREFERREDDROPEFFECT), nsnull, &tempOutData, &tempDataLen);

tempOutData should be freed.

The memory leak is only hit when Windows deicdes to set a preferred effect on the data source, which doesn't happen often.

Windows does set it sometimes when dragging from Windows explorer and always when dragging from an FTP site.


8 years ago
Blocks: 296528
No longer depends on: 296528

Comment 1

8 years ago
Neil this is the mem leak you noticed, so I'm setting you as the reviewer :)
Attachment #553669 - Flags: review?(neil)
Attachment #553669 - Flags: review?(neil) → review+

Comment 3

8 years ago
Seems like this fell through the cracks!  I rebased and landed it on inbound:
Target Milestone: --- → mozilla9
Keywords: mlk
Whiteboard: [MemShrink]

Comment 4

8 years ago
> Seems like this fell through the cracks!  

Nah I'm just behind on pushing my tasks out.  I had about 30 ready to go  in but didn't have level 3 commit access until about 3 weeks ago.  My rate of task creation vs pushing is fixed now so I should eventually get caught up :)
If you want a hand catching up, there is always checkin-needed :-)

Comment 6

8 years ago
nah mostly I need to run through try and verify things are ok.  I'm getting close to caught up already.  I try to put about 10 to try per week to get caught up right now.  This bug and the related drag and drop series of bugs are next on my list, but all hands in the way :)

Comment 7

8 years ago
> I rebased and landed it on inbound

Thanks by the way :)
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.