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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzoD5mwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgru7NpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrvyjtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjsHOtwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzovrtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgztzy7QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzp7puQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzoLVpgsM


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

android-nexus5
android-nexus7v2
android-one
android-webview-nexus6

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

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

Suspected Commit
  Author : Camillo Bruni
  Commit : c503b80595ded0e30ca9264689e026de07ce6f93
  Date   : Fri Jun 23 13:12:06 2017
  Subject: [runtime] Enable eager boilerplate creation again

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_social/load_social_tumblr
  Change       : 3.83% | 85406506.6667 -> 88680405.3333

Revision                           Result                   N
chromium@481866                    85406507 +- 1298452      6      good
chromium@481929                    85843755 +- 734596       6      good
chromium@481960                    85760981 +- 857316       6      good
chromium@481962                    85520512 +- 858650       6      good
chromium@481963                    85200683 +- 1451210      6      good
chromium@481963,v8@2b99d09e62      85626325 +- 1425477      6      good
chromium@481963,v8@c503b80595      88878720 +- 536050       6      bad       <--
chromium@481963,v8@28d6d14ad5      88701227 +- 2626059      6      bad
chromium@481964                    89390720 +- 1430286      6      bad
chromium@481968                    88869675 +- 896696       6      bad
chromium@481976                    89067819 +- 593292       6      bad
chromium@481991                    88680405 +- 1868549      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=load.social.tumblr system_health.memory_mobile

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

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


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