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

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


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

android-nexus5X
android-one

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

I created this to see where catapult sends bug reports for triaged alerts. I figured I'd be able to close it myself but it doesn't look that way. This can be closed/deleted to remove the association from the alert.

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

Suspected Commit
  Author : Alexandr Ilin
  Commit : 698e803c4335c3e9429f580851a580b18e7daef0
  Date   : Thu Nov 16 21:07:36 2017
  Subject: Revert "Enable SpeculativePreconnect Field Trial Testing"

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_news/browse_news_qq
  Change       : 8.82% | 26782853.7143 -> 29143828.8889

Revision             Result                   N
chromium@517139      26782854 +- 4923878      14      good
chromium@517182      26903763 +- 5592204      14      good
chromium@517188      27285060 +- 7308478      21      good
chromium@517190      26123244 +- 0.0          6       good
chromium@517191      29765664 +- 0.0          6       bad       <--
chromium@517193      29366443 +- 3658922      14      bad
chromium@517204      29765664 +- 0.0          6       bad
chromium@517225      29143829 +- 3485349      9       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.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/8961662091146852384


For feedback, file a bug with component Speed>Bisection