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

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


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

android-nexus6

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

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

Suspected Commit
  Author : mvstanton
  Commit : b8294aaa978e972978b8d82cedf63befad5d7af1
  Date   : Thu Jan 12 11:29:09 2017
  Subject: [TypeFeedbackVector] Root literal arrays in function literals slots

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/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 5.57% | 10303384.6667 -> 10876808.6667

Revision                           Result                   N
chromium@443389                    10303385 +- 347363       6       good
chromium@443396                    10314291 +- 340907       6       good
chromium@443400                    10306011 +- 362650       6       good
chromium@443400,v8@2bca05685f      10334930 +- 515190       14      good
chromium@443400,v8@b8294aaa97      10676643 +- 1566474      21      bad       <--
chromium@443400,v8@81c62e070b      10715897 +- 1186377      14      bad
chromium@443400,v8@9884fb91e1      10841248 +- 229274       9       bad
chromium@443400,v8@aa75904e3c      10884155 +- 7085.26      6       bad
chromium@443401                    10811680 +- 668171       9       bad
chromium@443402                    10874650 +- 58717.8      6       bad
chromium@443403                    10864665 +- 68178.8      6       bad
chromium@443416                    10814060 +- 612764       9       bad
chromium@443443                    10876809 +- 61682.3      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.yandex.ru.touchsearch.text.science memory.top_10_mobile_stress

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

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


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