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

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


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

android-nexus5
android-nexus7v2

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

=== Auto-CCing suspected CL author ccameron@chromium.org ===

Hi ccameron@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Christopher Cameron
  Commit : 1894d423068be735560e0171922c833c4091b5d1
  Date   : Wed Jun 28 06:31:03 2017
  Subject: color: Enable color correct rendering by default

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_social/load_social_tumblr
  Change       : 13.08% | 85823488.0 -> 97051989.3333

Revision             Result                   N
chromium@482883      85823488 +- 414486       6      good
chromium@482897      85910869 +- 672609       6      good
chromium@482901      85823488 +- 490427       6      good
chromium@482903      85790720 +- 620000       6      good
chromium@482904      97019221 +- 487499       6      bad       <--
chromium@482911      96769365 +- 2598928      6      bad
chromium@482939      97051989 +- 457971       6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.social.tumblr system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8963640429699861936


For feedback, file a bug with component Speed>Bisection

This CL is from 5 months ago... we should not be filing bugs with that kind of latency.

Furthermore, the graph only goes from 2017-6-28 to 2017-7-11, there were lots of fixes that went in after that.