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

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


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

android-nexus6

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

=== 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_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 0.66% | 3329148.0 -> 3351157.33333

Revision                           Result                  N
chromium@443389                    3329148 +- 219.089      6      good
chromium@443396                    3329067 +- 297.223      6      good
chromium@443400                    3329193 +- 29.2119      6      good
chromium@443400,v8@2bca05685f      3333875 +- 164.479      6      good
chromium@443400,v8@81c62e070b      3332115 +- 674.345      6      good
chromium@443400,v8@29e6218b7f      3332017 +- 533.117      6      good
chromium@443400,v8@9884fb91e1      3356444 +- 0.0          6      bad       <--
chromium@443400,v8@aa75904e3c      3356457 +- 69.3782      6      bad
chromium@443401                    3351108 +- 0.0          6      bad
chromium@443402                    3351157 +- 270.21       6      bad
chromium@443403                    3351236 +- 328.487      6      bad
chromium@443416                    3351207 +- 341.791      6      bad
chromium@443443                    3351157 +- 270.21       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=https.mobile.twitter.com.justinbieber.skip.interstitial.true memory.top_10_mobile_stress

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

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


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