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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=34e3e64aab0ee319f1dfb52395583be4533a8e71e87e93610e4ce3e386c49d4c


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

perf-go-phone-1024

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

=== Auto-CCing suspected CL author clank-buildbot@google.com ===

Hi clank-buildbot@google.com, 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 : clank-autoroller
  Commit : 24cae43d5e8dd1ea8fcb4b73b9d772bdb62cce71
  Date   : Sat Jun 30 01:47:51 2018
  Subject: Roll to 571706

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_shopping/browse_shopping_amazon
  Change       : 2.48% | 22995988.6667 -> 23567202.0

Revision                                       Result                   N
android-chrome@6e5ba20887                      22995989 +- 120232       6      good
android-chrome@23ce5c27b6                      22780003 +- 333855       6      good
android-chrome@23ce5c27b6,chromium@571698      23015316 +- 213176       6      good
android-chrome@23ce5c27b6,chromium@571703      23161560 +- 223327       9      good
android-chrome@23ce5c27b6,chromium@571705      23022337 +- 204800       6      good
android-chrome@23ce5c27b6,chromium@571706      23043213 +- 191980       6      good
android-chrome@24cae43d5e                      23744327 +- 332292       6      bad       <--
android-chrome@8dba9381aa                      23567202 +- 87498.9      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.amazon system_health.memory_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8942005798520755376


For feedback, file a bug with component Speed>Bisection

Assigned, but no owner or component? Please find a component and/or owner