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

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


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

android-nexus5
android-nexus6
android-nexus7v2

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

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

Suspected Commit
  Author : Tsuyoshi Horo
  Commit : e9cdaa227686d4e995569173d451cab0767ac48f
  Date   : Mon Nov 27 09:57:08 2017
  Subject: Add PWAFullCodeCache to fieldtrial_testing_config.json

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_news/browse_news_washingtonpost
  Change       : 25.89% | 5158866.66667 -> 6494408.0

Revision             Result                  N
chromium@519198      5158867 +- 4352.85      6      good
chromium@519250      5160206 +- 3735.15      6      good
chromium@519257      5159245 +- 3268.74      6      good
chromium@519260      5160011 +- 4223.28      6      good
chromium@519261      6494994 +- 2655.8       6      bad       <--
chromium@519262      6494537 +- 3314.72      6      bad
chromium@519263      6494421 +- 3752.33      6      bad
chromium@519276      6494143 +- 3469.72      6      bad
chromium@519302      6495479 +- 2036.87      6      bad
chromium@519405      6494408 +- 2955.17      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.washingtonpost 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/8961606604533851424


For feedback, file a bug with component Speed>Bisection