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

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


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

health-plan-clankium-phone

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 2e87ba2f2c31d81aedd027b2f68a7f2014410904
  bad_revision : b5896b295b3238c960714f1aef991e022c0a45a0

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_nytimes
  Change       : 3.95% | 9165114.66667 -> 9525700.66667

Revision                                       Result                  N
android-chrome@b5f70f02d5                      9165115 +- 77181.4      9       good
android-chrome@b5f70f02d5,chromium@573112      9243762 +- 117058       14      good
android-chrome@b5f70f02d5,chromium@573146      9156370 +- 56667.1      6       good
android-chrome@b5f70f02d5,chromium@573162      9214860 +- 123309       9       good
android-chrome@b5f70f02d5,chromium@573170      9501319 +- 146168       9       bad
android-chrome@b5f70f02d5,chromium@573178      9556692 +- 272918       9       bad
android-chrome@9245133ef9                      9501897 +- 143830       6       bad
android-chrome@66d4bec26b                      9516729 +- 235167       6       bad
android-chrome@664beaddad                      9525701 +- 201255       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes 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/8941217268487500096


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_nytimes


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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes 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/8940855877293407264


For feedback, file a bug with component Speed>Bisection

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

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

=== Auto-CCing suspected CL author nednguyen@google.com ===

Hi nednguyen@google.com, 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 : Nghia Nguyen
  Commit : 9eaedb7fa00f7b1c3bba87eeb82f75e7a147f8d2
  Date   : Sat Jul 07 16:13:23 2018
  Subject: Set non blocking I/O read on ts_proxy subprocess stdout to make sure the timeout

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_nytimes
  Change       : 4.02% | 9183236.88889 -> 9544640.66667

Revision                                                           Result                  N
android-chrome@b5f70f02d5                                          9183237 +- 80902.3      9       good
android-chrome@b5f70f02d5,chromium@573112                          9298613 +- 105674       9       good
android-chrome@b5f70f02d5,chromium@573146                          9200299 +- 77446.2      6       good
android-chrome@b5f70f02d5,chromium@573162                          9252931 +- 131843       9       good
android-chrome@b5f70f02d5,chromium@573166                          9274917 +- 152571       14      good
android-chrome@b5f70f02d5,chromium@573168                          9193691 +- 149401       6       good
android-chrome@b5f70f02d5,chromium@573169                          9158079 +- 93230.8      6       good
android-chrome@b5f70f02d5,chromium@573169,catapult@9eaedb7fa0      9376805 +- 67945.5      6       bad       <--
android-chrome@b5f70f02d5,chromium@573170                          9491779 +- 105408       9       bad
android-chrome@b5f70f02d5,chromium@573178                          9501624 +- 131281       9       bad
android-chrome@9245133ef9                                          9410404 +- 210455       9       bad
android-chrome@66d4bec26b                                          9376701 +- 137779       9       bad
android-chrome@664beaddad                                          9544641 +- 210168       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes 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/8940853524082905312


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news/load_news_nytimes


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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.nytimes 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/8940853500487042624


For feedback, file a bug with component Speed>Bisection