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

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


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

android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: d95e4951a3bab57b4839e3a3d7e64d43c8079d42
  bad_revision : 19bd384f656790e8e409086b5b97a53b3a6f5921

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 6.09% | 34083457.8333 -> 36158482.1667

Revision             Result                   N
chromium@482896      34083458 +- 811202       6      good
chromium@482902      34330583 +- 558890       6      good
chromium@482905      35861456 +- 510474       6      bad
chromium@482907      36158482 +- 1054740      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

=== 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_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 7.25% | 33622988.1667 -> 36060387.0

Revision             Result                   N
chromium@482902      33622988 +- 1456887      6      good
chromium@482903      34077096 +- 1184814      6      good
chromium@482904      35640972 +- 739487       6      bad       <--
chromium@482905      36060387 +- 1061444      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection