Comment #18 on issue 20067 by [email protected]: Canvas - memory leaks on getImageData http://code.google.com/p/chromium/issues/detail?id=20067
Precisely---when we observe big memory usage, we force GC to clean up the garbage. Regarding canvas API: we might be more agressive in collecting garbage for canvases, but it's always a compromise between speed/memory usage. Anyway, good to know it's not a problem for you any more. -- 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
