Closed
Bug 831791
Opened 11 years ago
Closed 11 years ago
possible memory leak in CompositorParent in SampleValue
Categories
(Core :: Graphics, defect)
Tracking
()
People
(Reporter: samuel.gallacier, Assigned: samuel.gallacier)
References
Details
Attachments
(1 file, 1 obsolete file)
879 bytes,
patch
|
dzbarsky
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20130115 Firefox/20.0 Build ID: 20130115042018 Steps to reproduce: Using css transform (translateX) of a <p> element (scrolling text) Actual results: In method SampleValue in CompositorParent.cpp (gfx/layers/ipc/), a InfallibleTArray<TransformFunction> object is constructed, and copied in a Animatable. The object seem never been destructed. The code is like: InfallibleTArray<TransformFunction>* functions = new InfallibleTArray<TransformFunction>(); functions->AppendElement(TransformMatrix(transform)); *aValue = *functions; Perhaps it should be : InfallibleTArray<TransformFunction> functions; functions.AppendElement(TransformMatrix(transform)); *aValue = functions;
Comment 1•11 years ago
|
||
Not sure what this code is supposed to be doing but it does look like there's a memory leak. CC'ing :dzbarksy who added it and :roc who r+'d it.
Component: General → Graphics
OS: Windows 7 → Android
Product: Firefox for Android → Core
Hardware: x86_64 → All
Version: Firefox 18 → Trunk
Comment 2•11 years ago
|
||
Yep, your suggestion seems correct.
Comment 3•11 years ago
|
||
Samuel, would you be willing to create a patch for review with your suggested change? There are instructions at https://developer.mozilla.org/en-US/docs/Developer_Guide/How_to_Submit_a_Patch (and specifically https://developer.mozilla.org/en-US/docs/Creating_a_patch_that_can_be_checked_in). If not let me know and I can do it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
Comment on attachment 704493 [details] [diff] [review] Correction proposal patch Samuel, the patch should really include a commit message and your author info (name + email) as well.
Attachment #704493 -
Flags: review?(dzbarsky)
Assignee | ||
Comment 6•11 years ago
|
||
Attachment #704493 -
Attachment is obsolete: true
Attachment #704493 -
Flags: review?(dzbarsky)
Comment 7•11 years ago
|
||
Comment on attachment 704556 [details] [diff] [review] Correction proposal patch Thanks! :)
Attachment #704556 -
Flags: review?(dzbarsky)
Comment 8•11 years ago
|
||
Comment on attachment 704556 [details] [diff] [review] Correction proposal patch Looks good to me. Make sure you put "r=dzbarsky" in your commit message.
Attachment #704556 -
Flags: review?(dzbarsky) → review+
Comment 9•11 years ago
|
||
The person landing it can do that. Inbound is closed currently so marking as checkin-needed.
Keywords: checkin-needed
Comment 10•11 years ago
|
||
Landed on inbound: https://hg.mozilla.org/integration/mozilla-inbound/rev/f92a3d2c1e5b
Assignee: nobody → samuel.gallacier
Keywords: checkin-needed
Comment 11•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f92a3d2c1e5b
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla21
Comment 12•11 years ago
|
||
Should we consider uplift this to b2g18? Leaking a object for each animation composition seems pretty bad.
Comment 13•11 years ago
|
||
Sounds like a good idea to me. It's a simple enough patch.
Updated•11 years ago
|
blocking-b2g: --- → tef?
Comment 14•11 years ago
|
||
I spoke about this with kats via IRC and he re-iterated his thinking that this was low risk and worth the reward.
blocking-b2g: tef? → tef+
Updated•11 years ago
|
Keywords: checkin-needed
Comment 15•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/6fecf538bfcb https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_0/rev/7cb579ad7aed
status-b2g18:
--- → fixed
status-firefox19:
--- → wontfix
status-firefox20:
--- → wontfix
status-firefox21:
--- → fixed
Keywords: checkin-needed
Comment 16•11 years ago
|
||
Landed on mozilla-b2g18/gaia master prior to the 1/25 branching to mozilla-b2g18_v1_0_0/v1.0.0, updating status-b2g-v1.0.0 to fixed.
status-b2g18-v1.0.0:
--- → fixed
Comment 17•11 years ago
|
||
scratch the previous comment - it got uplifted yesterday to the right branches - still fixed.
You need to log in
before you can comment on or make changes to this bug.
Description
•