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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxPi-8woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghPGe8AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghNmdqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxNzhtQkM


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

chromium-rel-mac11-air
win-high-dpi
win-zenbook

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : blink_perf.canvas
  Metric       : getImageData/getImageData

Revision             Result                  N
chromium@451764      281.007 +- 19.5472      21      good
chromium@451845      282.964 +- 9.8747       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.canvas

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8986733505898536400

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5874661780357120


| 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 Speed>Bisection.  Thank you!

Graphs seem to have recovered. Assuming issue was fixed already.