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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggrDlrQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDggrqFpwsM


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

android-nexus5
android-nexus7v2

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

=== 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_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_tools/load_tools_docs
  Change       : 22.99% | 66245778.2857 -> 82017718.8571

Revision             Result                    N
chromium@463574      66245778 +- 684006        14      good
chromium@463585      66135381 +- 82464.3       6       good
chromium@463590      66257351 +- 783620        9       good
chromium@463591      75774635 +- 22495139      6       bad       <--
chromium@463592      81539072 +- 16832912      6       bad
chromium@463593      74385636 +- 27153211      9       bad
chromium@463595      84501845 +- 68212.0       6       bad
chromium@463615      82490254 +- 17388621      9       bad
chromium@463657      75855774 +- 41892324      21      bad
chromium@463741      82017719 +- 23707862      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs system_health.memory_mobile

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

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


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