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

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


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

android-one

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

=== Auto-CCing suspected CL author danno@chromium.org ===

Hi danno@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : danno
  Commit : 8e19a2c4972bb7c3aae723c37999bedd3f8343dc
  Date   : Tue Jan 10 01:48:11 2017
  Subject: [stubs] Ensure generated CalculateNewElementsCapacity is identical to runtime version

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_http_search_yahoo_com_search__ylt_p_google
  Change       : 2.59% | 5389115.33333 -> 5528830.66667

Revision                           Result                  N
chromium@442432                    5389115 +- 91304.7      6      good
chromium@442476                    5427583 +- 71046.0      6      good
chromium@442498                    5401635 +- 83895.6      6      good
chromium@442509                    5414936 +- 82490.1      6      good
chromium@442509,v8@5560bbb498      5401951 +- 84581.3      6      good
chromium@442509,v8@8e19a2c497      5529361 +- 171552       6      bad       <--
chromium@442510                    5480911 +- 2999.66      6      bad
chromium@442511                    5474805 +- 30748.8      6      bad
chromium@442512                    5504494 +- 134448       6      bad
chromium@442514                    5479523 +- 377.843      6      bad
chromium@442519                    5528831 +- 170891       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.search.yahoo.com.search..ylt.p.google memory.top_10_mobile_stress

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

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


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

This bug has an owner, but was in a state that our triage picked up. Marking as Assigned.

The graph is pretty flaky, and since the regression the pre-regression values have been reached again, although it's hard to tell from the graph.