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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx9v74wsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp8bjtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx_WZ7AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgx-upswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp8v5uQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgp8b5pQoM


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

android-nexus9

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

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : [wasm] OOB traps: build protected instruction list during codegen
Author  : eholk
Commit description:
  
During codegen, we build a list mapping protected instructions to their
associated landing pads. This will ultimately by used by the signal handler to
recover from out of bounds faults and throw a JS exception.

This is mostly pulled from my larger in-progress CL at
https://codereview.chromium.org/2371833007/.

BUG= https://bugs.chromium.org/p/v8/issues/detail?id=5277

Review-Url: https://codereview.chromium.org/2500443004
Cr-Commit-Position: refs/heads/master@{#41400}
Commit  : bf35d15e5265f2d6ac74a594876d73ced535d8d1
Date    : Wed Nov 30 22:32:03 2016


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N   Good?
chromium@435509                5274704  282480   18  good
chromium@435509,v8@9b20a7b7a3  5282932  405438   27  good
chromium@435509,v8@bf35d15e52  5315541  306783   18  bad    <--
chromium@435510                5316597  18732.5  5   bad
chromium@435511                5333362  36813.6  5   bad
chromium@435512                5374134  178075   5   bad
chromium@435515                5349456  137312   5   bad
chromium@435520                5444699  148051   5   bad
chromium@435531                5314622  11534.7  5   bad
chromium@435553                5413730  189674   5   bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 671238

Test Command: 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
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
Relative Change: 2.83%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2304
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994097155238644656


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5903286199123968

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