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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6oLLzwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6qPEsgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6vTf-AsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6vuJsAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6pus-ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6ozp_AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6se8pwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg6rCp8QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqs7fxwsM


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

android-nexus5
android-nexus5X

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

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

Suspected Commit
  Author : Yutaka Hirano
  Commit : 823d5c738187627cbe218f01ddac6f383bcaaba8
  Date   : Fri May 12 09:29:18 2017
  Subject: Set URLResponseBodyConsumer::kMaxNumConsumedBytesInTask to 32K

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 26.70% | 32380510.6667 -> 41027044.0

Revision             Result                   N
chromium@471256      32380511 +- 2251315      6      good
chromium@471257      41351993 +- 2251315      6      bad       <--
chromium@471258      41676943 +- 1779821      6      bad
chromium@471260      41351993 +- 2251315      6      bad
chromium@471264      40702095 +- 2251315      6      bad
chromium@471272      40702095 +- 2251315      6      bad
chromium@471287      41027044 +- 2387880      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 memory.top_10_mobile

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

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


| 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!