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

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


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

android-nexus7v2

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                  N
chromium@443343      8103371 +- 985298       21      good
chromium@443443      8182416 +- 1244852      21      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.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile

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

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


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

Blocking on crbug.com/675639 for no memory.top_10_* repro

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

=== 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_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 6.88% | 7988651.33333 -> 8538126.66667

Revision                           Result                  N
chromium@443350                    7988651 +- 131075       6      good
chromium@443397                    8010077 +- 74049.9      6      good
chromium@443400                    7987966 +- 136015       6      good
chromium@443400,v8@2bca05685f      7998869 +- 97259.0      6      good
chromium@443400,v8@b8294aaa97      8472314 +- 17322.2      6      bad       <--
chromium@443400,v8@81c62e070b      8515457 +- 63557.6      6      bad
chromium@443400,v8@9884fb91e1      8581326 +- 82957.1      6      bad
chromium@443400,v8@aa75904e3c      8524100 +- 537681       9      bad
chromium@443401                    8618763 +- 135716       6      bad
chromium@443402                    8419784 +- 429455       6      bad
chromium@443403                    8644957 +- 97043.7      6      bad
chromium@443409                    8626077 +- 117200       6      bad
chromium@443420                    8633701 +- 128927       6      bad
chromium@443443                    8538127 +- 531987       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 memory.top_10_mobile

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

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


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

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                  N
chromium@443343      8103371 +- 985298       21      good
chromium@443443      8182416 +- 1244852      21      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.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile

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

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


| 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 Speed>Bisection.  Thank you!