All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=623590

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgot3opgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoua9tgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgov31tgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwuuJpAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgopaasQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgov3hpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgotu4tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgov2GugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoujZrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoqyCrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgovmLtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoob1swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoq3-ugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgopnktgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwp-BuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgooLVoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgopnktgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgooLVoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgosjjqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwr3nsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwp2usQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoryGsAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgovqKoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwr6mpwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwr3pvwoM


Bot(s) for this bug's original alert(s):

android-nexus5X
android-nexus9
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-single
win-zenbook

Moving this nonessential bug to the next milestone.

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

Lan, can you follow up on this?

From the instructions (https://chromium.googlesource.com/chromium/src/+/master/tools/perf/docs/perf_regression_sheriffing.md):
"After your shift, please try to follow up on the bugs you filed weekly. Kick off new bisects if the previous ones failed, and if the bisect picks a likely culprit follow up to ensure the CL author addresses the problem. If you are certain that a specific CL caused a performance regression, and the author does not have an immediate plan to address the problem, please revert the CL."

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007036736974475328

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@401755  182.653  7.87206  18  good
chromium@401756  184.591  4.55907  18  bad

Bisect job ran on: winx64_zen_perf_bisect
Bug ID: 623590

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests blink_perf.canvas
Test Metric: putImageData/putImageData
Relative Change: 0.10%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_zen_perf_bisect/builds/273
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007036736974475328


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5238760208334848

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

This is recovered. Looks like it was 27543ee6015a5d358e3abdb6ffb6121f6c847e31	 which was reverted. sunnps, FYI.