Comment #17 on issue 20067 by lievenswouter: Canvas - memory leaks on getImageData http://code.google.com/p/chromium/issues/detail?id=20067
You are correct, indeed. As soon as it reaches more than ~256M, it suddenly shrinks - from a GC run, of course. Chrome 3 didn't seem to do that however, it went on past 400M (after which I killed the process, so I never reproduced an actual *crash*). Maybe the Canvas API should support a dispose method to avoid this, but that's obviously not your concern. Funny to see this was originally reported on the Mona Lisa GA thing. I saw that back when it was hot news. ---- Hey, no problem - I worked as compiler engineer for four years; I know how it feels to get positive feedback from your users for this kind of project. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings -- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
