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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgwtrH7wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_Pr6qwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_LnzogkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_IbSoAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg_MbvuwoM


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

android-nexus5
android-nexus6
android-nexus7v2
android-webview-nexus6

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

=== 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    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science
  Change       : 185.15% | 4789753.33333 -> 13658163.3333

Revision             Result                   N
chromium@463575      4789753 +- 1982670       6      good
chromium@463587      5093751 +- 2732860       6      good
chromium@463590      4581538 +- 1574922       6      good
chromium@463591      13365257 +- 277364       6      bad       <--
chromium@463592      13589385 +- 792890       6      bad
chromium@463593      13644603 +- 1005280      6      bad
chromium@463598      13666527 +- 883426       6      bad
chromium@463620      13541718 +- 755996       6      bad
chromium@463664      13658163 +- 1002196      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 memory.top_10_mobile_stress

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

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


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