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

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


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

android-nexus5

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4547
Failure reason: the build has failed due to infrastructure failure.

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

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

Suspected Commit
  Author : mvstanton
  Commit : 38602f1ff553b32815d34a05cd6d965f4fc20960
  Date   : Mon Jan 09 15:31:00 2017
  Subject: [FeedbackVector] Infrastructure for literal arrays in the vector.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_taobao
  Change       : 1.39% | 5333241.33333 -> 5407566.22222

Revision                           Result                  N
chromium@442253                    5333241 +- 352674       9      good
chromium@442299                    5249244 +- 435790       6      good
chromium@442311                    5255173 +- 417242       6      good
chromium@442312                    5374850 +- 3738.0       6      good
chromium@442312,v8@e7fc42796c      5310575 +- 354328       6      good
chromium@442312,v8@38602f1ff5      5450665 +- 51583.3      6      bad       <--
chromium@442313                    5446619 +- 87516.3      6      bad
chromium@442314                    5458631 +- 70340.5      6      bad
chromium@442317                    5440833 +- 65544.6      6      bad
chromium@442322                    5409183 +- 373272       9      bad
chromium@442344                    5459529 +- 4709.59      6      bad
chromium@442435                    5407566 +- 385084       9      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=load.search.taobao system_health.memory_mobile

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

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


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