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

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


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

health-plan-clankium-phone
perf-go-phone-1024

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

=== 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 : 009b09f9630f0f635a7cb857ab7dd6d02d39ba32
  Date   : Tue Jun 19 22:37:45 2018
  Subject: Update Orderfile.

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_tech/browse_tech_discourse_infinite_scroll
  Change       : 3.86% | 19923577.3333 -> 20692492.0

Revision                       Result                  N
android-chrome@132390eaab      19923577 +- 238845      6      good
android-chrome@0310138f7e      20083664 +- 153317      6      good
android-chrome@b78b852adc      20103053 +- 140655      6      good
android-chrome@e9f1214bba      20077636 +- 123451      6      good
android-chrome@6bd07f8e66      19949569 +- 206566      6      good
android-chrome@5b0fd46994      19902477 +- 159764      6      good
android-chrome@009b09f963      20433912 +- 157247      6      bad       <--
android-chrome@b268028c43      20692492 +- 122185      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.tech.discourse.infinite.scroll 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/8942758732045714928


For feedback, file a bug with component Speed>Bisection

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