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

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


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

android-nexus5X

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

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

Hi charliea@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 : Charlie Andrews
  Commit : 378b8d3cafcf8e3cac8e9ed98d496fc2a1ac9db3
  Date   : Tue Dec 19 21:23:18 2017
  Subject: Makes benchmark_smoke_unittest pull in expectations.config

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_news/load_news_qq
  Change       : 1.20% | 32248594.8571 -> 32636844.4444

Revision             Result                   N
chromium@525101      32248595 +- 1026383      14      good
chromium@525124      32187195 +- 495835       6       good
chromium@525135      32237029 +- 649159       9       good
chromium@525140      32120123 +- 563956       6       good
chromium@525143      32111760 +- 1101222      9       good
chromium@525144      32063461 +- 1009561      6       good
chromium@525145      32584458 +- 1274969      21      bad       <--
chromium@525188      32684103 +- 901497       14      bad
chromium@525274      32636844 +- 832609       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=load.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/8958520990835962528


For feedback, file a bug with component Speed>Bisection

I'm definitely not responsible for this regression: this was a Telemetry configuration change that was unrelated to Chrome. I'd try to bisect again.

It's recovered anyway, I don't think it's worth digging into it.