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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=dd85e245fba8893d0f3ead88ef00268cb46ca8f31d56b49b27aebea8774142c4


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

Win 7 Perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/119320a2e40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/119320a2e40000

Stop using color space xform canvas in Skia's picture backed images by brianosman@google.com
https://chromium.googlesource.com/chromium/src/+/530a1ad5eb14f098bc897aecce9f8d9cdc099ec1
thread_raster_cpu_time_per_frame: 0.2279 → 0.3358 (+0.108)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

We were able to reproduce this (noisily) today, but have not been able to isolate the diff.  Though these changes are relatively large, they're actually very small in the absolute sense (20µs here or there).  Since the diff is so small and we can't pin it down, I think we might just want to drop this.

 Issue 901392  has been merged into this issue.