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

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


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

android-nexus5X

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

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

Suspected Commit
  Author : titzer
  Commit : 9884fb91e15e5e85218886b67af410668a08c38b
  Date   : Thu Jan 12 12:04:35 2017
  Subject: [wasm] Enable WASM by default (--expose-wasm=true).

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 0.57% | 12768737.7778 -> 12842092.0

Revision                           Result                   N
chromium@443377                    12768738 +- 68567.3      9       good
chromium@443393                    12777299 +- 73724.9      9       good
chromium@443397                    12788869 +- 131495       14      good
chromium@443399                    12764791 +- 53653.5      6       good
chromium@443400                    12779551 +- 96398.7      14      good
chromium@443400,v8@2bca05685f      12787593 +- 192332       14      good
chromium@443400,v8@81c62e070b      12803819 +- 220647       21      good
chromium@443400,v8@29e6218b7f      12774669 +- 46076.1      6       good
chromium@443400,v8@9884fb91e1      12846747 +- 169647       14      bad       <--
chromium@443400,v8@aa75904e3c      12862639 +- 196699       14      bad
chromium@443401                    12840061 +- 109167       9       bad
chromium@443409                    12875224 +- 106764       6       bad
chromium@443441                    12842092 +- 84261.9      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=http.en.m.wikipedia.org.wiki.Science memory.top_10_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!