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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_qq

Revision             Result                   N
chromium@498815      34427534 +- 858568       21      good
chromium@499149      34434380 +- 1035689      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=browse.news.qq 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/8969252318265909552


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Khushal
  Commit : 7875d555052d5faeb68ccc586a3be2d183b2c215
  Date   : Wed Aug 30 19:40:12 2017
  Subject: cc: Only checker images required for pending tree activation.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_qq
  Change       : 0.83% | 34202312.0 -> 34486966.2857

Revision             Result                   N
chromium@498451      34202312 +- 1250122      14      good
chromium@498549      34076907 +- 335371       6       good
chromium@498562      34197337 +- 291127       6       good
chromium@498568      34176755 +- 201103       6       good
chromium@498570      34260417 +- 241878       6       good
chromium@498571      34553677 +- 771871       9       bad       <--
chromium@498574      34605200 +- 491841       9       bad
chromium@498598      34617557 +- 668848       9       bad
chromium@498646      34513790 +- 664731       14      bad
chromium@498841      34530869 +- 562403       9       bad
chromium@499230      34486966 +- 584795       14      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=browse.news.qq 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/8969179723959262640


For feedback, file a bug with component Speed>Bisection