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

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


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

perf-go-phone-1024
perf-go-phone-512

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: cc05af85f063f98f51ee43fa556deb8779ba3df0
  bad_revision : 6b91daa8df790da14d7ba894b7c769a227736653

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_news/browse_news_qq
  Change       : 4.22% | 44454570.6667 -> 46329856.0

Revision                                       Result                  N
android-chrome@cd7b16c40c                      44454571 +- 449892      6      good
android-chrome@cd7b16c40c,chromium@567124      44847787 +- 261470      6      good
android-chrome@cd7b16c40c,chromium@567125      46704640 +- 226916      6      bad
android-chrome@cd7b16c40c,chromium@567126      46745600 +- 302902      6      bad
android-chrome@cd7b16c40c,chromium@567128      46432256 +- 378600      6      bad
android-chrome@cd7b16c40c,chromium@567133      46637056 +- 156958      6      bad
android-chrome@cd7b16c40c,chromium@567145      46975659 +- 375017      6      bad
android-chrome@306d8fee9b                      46536704 +- 237579      6      bad
android-chrome@b937761e15                      46769493 +- 455299      6      bad
android-chrome@6b97f109ea                      46329856 +- 149714      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.news.qq 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/8943021642838501568


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Ben Wagner
  Commit : d34b8a80f30a176ecf1c01ae7220b5f8af636eb8
  Date   : Wed Jun 13 15:37:56 2018
  Subject: Always FreeType autohint when requested.

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/browse_news/browse_news_qq
  Change       : 4.77% | 44002645.3333 -> 46101845.3333

Revision                                                       Result                  N
android-chrome@cd7b16c40c                                      44002645 +- 449019      6      good
android-chrome@cd7b16c40c,chromium@567123                      44122112 +- 306440      6      good
android-chrome@cd7b16c40c,chromium@567124                      44034048 +- 534962      6      good
android-chrome@cd7b16c40c,chromium@567124,skia@5f4b09d523      44010837 +- 330691      6      good
android-chrome@cd7b16c40c,chromium@567124,skia@dc89f192c8      43842219 +- 340394      6      good
android-chrome@cd7b16c40c,chromium@567124,skia@d34b8a80f3      46043819 +- 236697      6      bad       <--
android-chrome@cd7b16c40c,chromium@567124,skia@6fbafc0afa      46065664 +- 443790      6      bad
android-chrome@cd7b16c40c,chromium@567124,skia@f18c756360      46098432 +- 265296      6      bad
android-chrome@cd7b16c40c,chromium@567125                      46091605 +- 340904      6      bad
android-chrome@cd7b16c40c,chromium@567128                      45965995 +- 168333      6      bad
android-chrome@cd7b16c40c,chromium@567133                      46196736 +- 290738      6      bad
android-chrome@cd7b16c40c,chromium@567145                      46023339 +- 274064      6      bad
android-chrome@306d8fee9b                                      46000128 +- 424902      6      bad
android-chrome@b937761e15                                      46101845 +- 540844      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.news.qq 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/8942756228579800800


For feedback, file a bug with component Speed>Bisection