In patch (https://codereview.chromium.org/1938103002/), we set some idleTaskCompleteTimeoutDelay for canvas.toBlob. We want to measure how often this timeout delay is hit.
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/8c59e014125ad442b32c21b1724add603b489cc2 commit 8c59e014125ad442b32c21b1724add603b489cc2 Author: xidachen <xidachen@chromium.org> Date: Fri Jul 01 00:17:01 2016 Track performance of toBlob and its complete timeout delay This CL does two things: 1. Track the performance of a toBlob API call. Because toBlob has a call back, so we put a timer in the CanvasAsyncToBlob class. 2. Track how often the complete timeout delay happens in toBlob calls. BUG= 612585 , 608815 Review-Url: https://codereview.chromium.org/2039673002 Cr-Commit-Position: refs/heads/master@{#403362} [modify] https://crrev.com/8c59e014125ad442b32c21b1724add603b489cc2/third_party/WebKit/Source/core/html/HTMLCanvasElement.cpp [modify] https://crrev.com/8c59e014125ad442b32c21b1724add603b489cc2/third_party/WebKit/Source/core/html/canvas/CanvasAsyncBlobCreator.cpp [modify] https://crrev.com/8c59e014125ad442b32c21b1724add603b489cc2/third_party/WebKit/Source/core/html/canvas/CanvasAsyncBlobCreator.h [modify] https://crrev.com/8c59e014125ad442b32c21b1724add603b489cc2/third_party/WebKit/Source/core/html/canvas/CanvasAsyncBlobCreatorTest.cpp [modify] https://crrev.com/8c59e014125ad442b32c21b1724add603b489cc2/tools/metrics/histograms/histograms.xml
Comment 1 by xidac...@chromium.org
, Jun 7 2016Owner: xidac...@chromium.org
Status: Started (was: Assigned)