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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_NeWjQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_PnWpgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_K_nswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggujrowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_PnW5ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_P2SpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggvTE6AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggrre-ggM


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

android-nexus5
android-one
android-webview-nexus5X

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

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

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

Suspected Commit
  Author : delphick
  Commit : d8ade60fbe0ea954ecd5f186c36e6d0ac045c28c
  Date   : Tue Apr 11 09:56:28 2017
  Subject: No longer clamp setTimeout(..., 0) to 1ms.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background_search/background_search_google
  Change       : 55.79% | 19013632.0 -> 29622272.0

Revision             Result                  N
chromium@463554      19013632 +- 190629      6      good
chromium@463582      19039573 +- 179727      6      good
chromium@463589      19039573 +- 179727      6      good
chromium@463590      19013632 +- 190629      6      good
chromium@463591      29622272 +- 190629      6      bad       <--
chromium@463593      29622272 +- 190629      6      bad
chromium@463596      29622272 +- 190629      6      bad
chromium@463609      29570389 +- 142087      6      bad
chromium@463664      29622272 +- 190629      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=background.search.google system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982420756041446448

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5578501635178496


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background_search/background_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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.search.google system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982420797197857632

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5604914866159616


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background_search/background_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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.search.google system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982280798561736656

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5604914866159616


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!