[Webkit-unassigned] [Bug 235002] readPixels directly to ArrayBuffer has very high CPU usage
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Mar 30 13:20:09 PDT 2022
https://bugs.webkit.org/show_bug.cgi?id=235002
Gregg Tavares <gman at chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gman at chromium.org
--- Comment #9 from Gregg Tavares <gman at chromium.org> ---
fyi: In my experiments if you render to your own texture (via a framebuffer) you'll get your speed back. Based on the trace above my guess it's the IOSurfaceLock/Unlock causing the slowdown. That's only needed for reading the canvas itself, not for reading your own texture.
Of course we should optimize reading the canvas too, just pointing out a possible workaround.
--
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/20220330/09ce84a0/attachment-0001.htm>
More information about the webkit-unassigned
mailing list