canvas to canvas drawImage performs flush of the source canvas each time |
||
Issue descriptionWhen an accelerated 2D canvas is used as a source image in a drawImage call, we call Canvas2DLayerBridge::flush(), which consume about 50 microseconds of CPU each time when there are no actual draw calls to be flushed. We should do an early exit based on whether didDraw was called since the previous flush.
,
Jan 16 2017
,
Jan 16 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a4eab9aa9b5cbeb5e9dde2ce1eb0ecd6313c8f6c commit a4eab9aa9b5cbeb5e9dde2ce1eb0ecd6313c8f6c Author: junov <junov@chromium.org> Date: Mon Jan 16 22:28:52 2017 Adding test to verify that Canvas2DLayerBridge flushes only when required This is a follow-up to CL: https://codereview.chromium.org/2637553002/ It adds a unit test to validate the functionality of the new optimization that prevents redundant flushing. BUG= 681200 Review-Url: https://codereview.chromium.org/2636973002 Cr-Commit-Position: refs/heads/master@{#443955} [modify] https://crrev.com/a4eab9aa9b5cbeb5e9dde2ce1eb0ecd6313c8f6c/third_party/WebKit/Source/platform/graphics/Canvas2DLayerBridge.h [modify] https://crrev.com/a4eab9aa9b5cbeb5e9dde2ce1eb0ecd6313c8f6c/third_party/WebKit/Source/platform/graphics/Canvas2DLayerBridgeTest.cpp |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jan 16 2017