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

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


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

android-nexus5
android-nexus5X
android-one

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

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

Hi japhet@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 : Nate Chapin
  Commit : a1bfc9f9cb531a1d5dd1e28b51a38b728ece1235
  Date   : Mon Dec 18 21:42:32 2017
  Subject: SetResource() in ResourceFetcher for FontResources

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_cnn
  Change       : 14.45% | 84496948.0 -> 96707240.0

Revision             Result                   N
chromium@524787      84496948 +- 908715       6      good
chromium@524805      85281987 +- 810204       6      good
chromium@524807      84164291 +- 998747       6      good
chromium@524808      96753545 +- 1106144      6      bad       <--
chromium@524810      96646510 +- 629886       6      bad
chromium@524814      96545160 +- 1480800      6      bad
chromium@524822      97064264 +- 1311121      6      bad
chromium@524857      96958003 +- 611053       6      bad
chromium@524926      96707240 +- 773802       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=browse.news.cnn 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/8959561124793979104


For feedback, file a bug with component Speed>Bisection

Issue 797078 has been merged into this issue.

Issue 797088 has been merged into this issue.

Issue 797079 has been merged into this issue.

Issue 797103 has been merged into this issue.

Issue 797102 has been merged into this issue.

Issue 797106 has been merged into this issue.

https://chromium.googlesource.com/chromium/src/+/3a87be14e46d7d1946da2277ba03751e96fe0e04 resolved these regressions.