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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_chrome/load_chrome_blank

Revision             Result                  N
chromium@508492      16831657 +- 471737      21      good
chromium@508578      16881754 +- 346258      21      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 --story-filter=load.chrome.blank 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/8965206505787612240


For feedback, file a bug with component Speed>Bisection

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

Kicked a bisect on a wider range: https://chromeperf.appspot.com/buildbucket_job_status/8964931286182738096

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

Suspected Commit
  Author : sunxd
  Commit : 48493dc45de06867eec97e7944f56d511e3c4578
  Date   : Thu Oct 12 20:25:14 2017
  Subject: cc: make solid color picture layer tiling respect device scale factor

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_chrome/load_chrome_blank
  Change       : 1.66% | 16601277.3333 -> 16877225.3333

Revision             Result                  N
chromium@508377      16601277 +- 346080      6       good
chromium@508433      16541652 +- 217032      6       good
chromium@508440      16625105 +- 451665      9       good
chromium@508441      16718370 +- 433029      14      good
chromium@508442      16879933 +- 333302      9       bad       <--
chromium@508444      16809359 +- 259612      6       bad
chromium@508447      16918259 +- 164030      6       bad
chromium@508461      16851208 +- 216440      6       bad
chromium@508488      16847020 +- 216322      9       bad
chromium@508599      16877225 +- 101638      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 --story-filter=load.chrome.blank 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/8964931286182738096


For feedback, file a bug with component Speed>Bisection