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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggrK8tQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_LnMpAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_JnL-goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_J3G8QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggpLx6wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggu3qsQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_K_n8wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_NftowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_JnLhgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggsKs1AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggtmXswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_I2HmggM


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

android-nexus5X
android-nexus6
android-nexus7v2
android-one

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

=== 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_nexus5X_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       : 48.72% | 18459200.0 -> 27453105.7778

Revision             Result                   N
chromium@463571      18459200 +- 9670789      9      good
chromium@463588      18441906 +- 9690078      9      good
chromium@463590      18984853 +- 9124953      6      good
chromium@463591      27509995 +- 274320       6      bad       <--
chromium@463593      27470400 +- 0.0          6      bad
chromium@463597      27457202 +- 111991       9      bad
chromium@463605      27490197 +- 108434       6      bad
chromium@463639      27470400 +- 0.0          6      bad
chromium@463706      27453106 +- 146746       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=background.search.google system_health.memory_mobile

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

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


| 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!