[Azure] Direct2D CreateGradientStops leaks Stops array

RESOLVED FIXED

Status

()

Core
Graphics
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: bas, Assigned: bas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P2])

Attachments

(1 attachment)

(Assignee)

Description

6 years ago
Created attachment 570484 [details] [diff] [review]
Use vector to store stops

I've found a memory leak in CreateGradientStops in the Azure D2D backend.
Attachment #570484 - Flags: review?(jmuizelaar)
Attachment #570484 - Flags: review?(jmuizelaar) → review+

Updated

6 years ago
Whiteboard: [MemShrink]
Whiteboard: [MemShrink] → [MemShrink:P2]
Backed out in https://hg.mozilla.org/integration/mozilla-inbound/rev/725022655d4f, see https://tbpl.mozilla.org/php/getParsedLog.php?id=7290634&tree=Mozilla-Inbound for Win7 opt and https://tbpl.mozilla.org/php/getParsedLog.php?id=7290815&tree=Mozilla-Inbound for Win7 debug
(Assignee)

Comment 2

6 years ago
That's what I get for not testing properly. Sorry for the hassle, will attach a new patch soon.
Bas, any progress here?
(Assignee)

Comment 4

6 years ago
I think the patch was landed as part of Azure-Thebes D2D. I'll double check.
Bas, any progress on the double-checking?  Actually, I'm going to be optimistic and assume this is fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.