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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguMLHtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2L67pAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguLmDuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguLSZuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2Kaa6QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2NuYuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2M-yuQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2K_LtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguJCS-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguOTopgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguKT3uwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2I__sQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguNqPpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguPDqvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguJ6SqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2P7AtQkM


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

android-nexus5X
android-webview-nexus6

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

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

Suspected Commit
  Author : fdoray
  Commit : b83be4ca0e00b50b17619adf7f7de275455e9852
  Date   : Mon Feb 13 16:39:47 2017
  Subject: Use TaskScheduler instead of WorkerPool in v8_platform.cc.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_hackernews
  Change       : 2.20% | 58700413.3333 -> 59994749.3333

Revision             Result                   N
chromium@449955      58700413 +- 874462       6      good
chromium@449967      58774141 +- 478335       6      good
chromium@449973      58792061 +- 606204       6      good
chromium@449975      58934397 +- 854042       9      good
chromium@449976      60051581 +- 1143125      6      bad       <--
chromium@449979      59994237 +- 831795       6      bad
chromium@450003      60167464 +- 1213517      6      bad
chromium@450050      59994749 +- 408861       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=browse.news.hackernews system_health.memory_mobile

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

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


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