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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmoqFvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmoXD7gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rDikQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtjjvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmvzKqgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmsPosgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmrzYqAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgmtGepAoM


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

android-nexus5X
android-webview-nexus5X

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

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

Suspected Commit
  Author : Yutaka Hirano
  Commit : f20d10a747ef558a18cdd6925df977352e477997
  Date   : Mon May 15 04:44:45 2017
  Subject: Revert "Set URLResponseBodyConsumer::kMaxNumConsumedBytesInTask to 32K"

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_chrome/browse_chrome_omnibox
  Change       : 68.43% | 48717216.0 -> 82053088.0

Revision             Result               N
chromium@471647      48717216 +- 0.0      6      good
chromium@471664      48717216 +- 0.0      6      good
chromium@471669      48717216 +- 0.0      6      good
chromium@471670      82053088 +- 0.0      6      bad       <--
chromium@471671      82053088 +- 0.0      6      bad
chromium@471673      82053088 +- 0.0      6      bad
chromium@471681      82053088 +- 0.0      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.chrome.omnibox system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979391022094677232

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6138989448265728


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!