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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzvSLqQkM


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

android-nexus6

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

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

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

Suspected Commit
  Author : Yutaka Hirano
  Commit : 84047549ac37bab70d7306566c912e59131f3e1f
  Date   : Mon Jun 19 04:16:15 2017
  Subject: [Loading] Save one post-task when the data pipe is ready on arrival

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_news/load_news_cnn
  Change       : 14.83% | 589045.777778 -> 676436.666667

Revision             Result                 N
chromium@480312      589046 +- 671.407      9       good
chromium@480329      595911 +- 92813.4      14      good
chromium@480338      597088 +- 34245.4      9       good
chromium@480340      588873 +- 415.795      6       good
chromium@480341      588943 +- 509.326      6       good
chromium@480342      662137 +- 52125.5      6       bad       <--
chromium@480346      658542 +- 95039.3      9       bad
chromium@480379      676437 +- 38192.3      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.cnn system_health.memory_mobile

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

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


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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/load_news/load_news_cnn
  Change       : 17.23% | 431443.714286 -> 505779.111111

Suspected Commit Range
  19 commits in range
  https://chromium.googlesource.com/chromium/src/+log/65400da28d6fc9221acdd2fffbbf4f459435e44e..06e980861f8b1a81c4d5da2f667f44336cab385d


Revision             Result                N
chromium@480312      431444 +- 257736      14       good
chromium@480322      410746 +- 184781      14       good
chromium@480323      ---                   ---      build failure
---                  ---                   ---      too many build failures to list
chromium@480340      ---                   ---      build failure
chromium@480341      473169 +- 386122      21       bad
chromium@480346      483822 +- 178805      14       bad
chromium@480379      505779 +- 257693      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.cnn system_health.memory_mobile

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

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


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