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

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


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

android-nexus5X

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

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

Suspected Commit
  Author : eholk
  Commit : 118c376fcbe483b155eec26f8d9192f8cb4b4721
  Date   : Mon Mar 13 22:12:23 2017
  Subject: [wasm] Initial signal handler

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 1.48% | 3607401.6 -> 3660757.33333

Revision                           Result                  N
chromium@456678                    3607402 +- 9005.6       5      good
chromium@456687                    3609085 +- 7453.44      6      good
chromium@456690                    3607749 +- 9368.8       6      good
chromium@456690,v8@118c376fcb      3644061 +- 253.403      6      bad       <--
chromium@456690,v8@3800ba6cc7      3643903 +- 861.88       6      bad
chromium@456690,v8@97254b0d23      3650913 +- 7443.68      6      bad
chromium@456690,v8@f20261bfb4      3646919 +- 36613.7      6      bad
chromium@456691                    3667389 +- 39990.0      6      bad
chromium@456692                    3649709 +- 7542.92      6      bad
chromium@456696                    3653968 +- 34978.5      6      bad
chromium@456713                    3660757 +- 48625.1      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

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

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


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