[Webkit-unassigned] [Bug 195325] Canvas elements not garbage collected immediately in Safari on iOS 12

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Jun 21 20:09:31 PDT 2022


--- Comment #15 from Dean Jackson <dino at apple.com> ---
Here is someone complaining and explaining the workaround: https://pqina.nl/blog/total-canvas-memory-use-exceeds-the-maximum-limit/
(although I'm not sure you have to clear the contents - just setting the dimensions should do that for you)

I think in the short term our options are A or B above.

Option A is definitely frustrating for developers. I sympathise :(

Option B is fine, until it isn't. The user might have entered a lot of information onto the page before it is killed by the system. Seems better to have a broken page than killing it completely.

Then again, we don't know how many pages would create so much canvas backing store to trigger a jetsam. I expect it is a small %.

For the moment I'm choosing option A, but looking out for good arguments in the comments.

You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220622/a02f05fa/attachment.htm>

More information about the webkit-unassigned mailing list