Was this the image bug that was fixed by modifying the cache?

@schenney
Sorry, I don't quite understand what you mean, could you please explain in more detail?

Sorry, I was not directing that question to troysdc@. Not too long ago junov@ landed a patch to change the cache size for images. I was wondering if that was the same issue as the one reported here.

@#2: This is a separate bug.

The problem here is that the rendering loop is leaking canvas objects, and the browser is exceeding canvas GPU resource limits before garbage collection is triggered. Therefore, at some point, canvases stop being GPU accelerated.

@junov
Thanks, now I know the reason. But how Can I fix it? For I am already removed canvas from canvasList and DOM.

There are two way you could fix this:

A) avoid creating temporary canvas objects. Instead, create a single canvas that you keep re-using until the end of time.

or

B) Set the size (width or height attribute) to 0 when you are done using the canvas.  That will release GPU resources immediately instead of waiting for the object to be garbage collected.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot