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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_search/load_search_google


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.search.google 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/8968030826967148864


For feedback, file a bug with component Speed>Bisection

Simon, looks like a lot of failures over the past two days, can you take a look?

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

Trying this again, provision devices failed but I see later runs that are green.

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

Suspected Commit
  Author : Timothy Loh
  Commit : e1ef417340c9ebfe3613c90b636f74f96c9efc4b
  Date   : Thu Sep 14 03:31:59 2017
  Subject: Enable modal permission prompts on android

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_search/load_search_google
  Change       : 10.87% | 48746496.0 -> 54044899.5556

Revision             Result                   N
chromium@501780      48746496 +- 0.0          9      good
chromium@501844      47416661 +- 7283804      6      good
chromium@501852      48746496 +- 0.0          6      good
chromium@501856      48746496 +- 0.0          6      good
chromium@501858      48746496 +- 0.0          6      good
chromium@501859      54931456 +- 0.0          6      bad       <--
chromium@501860      54931456 +- 0.0          6      bad
chromium@501876      54931456 +- 0.0          6      bad
chromium@501908      54044900 +- 7522681      9      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.search.google 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/8967919422611609488


For feedback, file a bug with component Speed>Bisection