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

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


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

android-nexus5X

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

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

Hi mgersh@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 : Miriam Gershenson
  Commit : dacc1537d0973365e5d04b49ea014f045712c4b6
  Date   : Thu Nov 09 19:44:29 2017
  Subject: Add MemoryDumpProvider for DnsConfigServicePosix::HostsReader

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_qq
  Change       : 1.66% | 37871894.6667 -> 38501188.0

Revision             Result                   N
chromium@515228      37871895 +- 296253       6       good
chromium@515244      37898178 +- 1043494      14      good
chromium@515246      37819485 +- 537019       6       good
chromium@515247      38678646 +- 560848       6       bad       <--
chromium@515249      38696946 +- 1236397      6       bad
chromium@515252      38308599 +- 1400115      14      bad
chromium@515260      38685401 +- 793505       6       bad
chromium@515291      38635309 +- 431149       6       bad
chromium@515354      38501188 +- 476660       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=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/8962733627600869472


For feedback, file a bug with component Speed>Bisection

Adding more data to the memory dump will use more memory. This will have no effect if not taking a memory dump.