[Webkit-unassigned] [Bug 20315] New: Memory leak with Canvas getImageData

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Aug 7 02:06:39 PDT 2008


https://bugs.webkit.org/show_bug.cgi?id=20315

           Summary: Memory leak with Canvas getImageData
           Product: WebKit
           Version: 526+ (Nightly build)
          Platform: Macintosh
               URL: http://www.cuppadev.co.uk/assets/canvas-quirk.html
        OS/Version: Mac OS X 10.5
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jamesu at gmail.com


I seem to be getting a rather predictable memory "leak" when using
getImageData() on a 2d Canvas Rendering Context.

Basically in my test case, i am calling putImageData(getImageData(...), ...)
every chance i can get. Memory usage climbs well into the 1 <-> 2gb range.

It should be noted that this occurs in other browsers too, though with varying
cut-off points (presumably when the garbage collection finally kicks in).

However it should also be noted that i am essentially running the same code in
a real app, i don't seem to encounter this issue (in WebKit r35620). For
reference, i have put a copy of this up at the following URL:

http://www.cuppadev.co.uk/hiscumm/webkit-canvas-mem/js_test.html

(search for "fastPaletteRemap" if you want the meat of it)

As for why this is, i am really stumped. So i can't really rely on it.

Any insight would be appreciated of course. :)


-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the webkit-unassigned mailing list