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

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


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

android-webview-nexus6

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

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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background_social/background_social_facebook


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.social.facebook system_health.memory_mobile

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

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


| 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/8981542173298367456

=== 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_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background_search/background_search_google
  Change       : 17.70% | 34404921.3333 -> 40495502.6667

Revision             Result                   N
chromium@462278      34404921 +- 748398       6      good
chromium@463052      34720313 +- 1466767      6      good
chromium@463439      34504761 +- 1392659      6      good
chromium@463536      35193231 +- 748894       6      good
chromium@463584      35248356 +- 489257       6      good
chromium@463590      35348879 +- 1342156      6      good
chromium@463591      41390479 +- 1207430      6      bad       <--
chromium@463592      41225956 +- 2136856      6      bad
chromium@463593      40915343 +- 1836995      6      bad
chromium@463596      40798095 +- 1609904      6      bad
chromium@463608      40863801 +- 1130886      6      bad
chromium@463632      41678393 +- 948379       6      bad
chromium@463825      41125945 +- 1218831      6      bad
chromium@465372      40495503 +- 875733       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-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/8981542173298367456

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


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