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

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


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

health-plan-webview-phone

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

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

Hi kylechar@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 : kylechar
  Commit : f77f6b8dba2776e23111c84c5d9333dbb03039fe
  Date   : Wed Jun 13 20:29:11 2018
  Subject: Fix UseSurfaceLayerForVideo GPU crash handling.

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_footprint_size_avg/background_news/background_news_nytimes
  Change       : 6.51% | 86316373.3333 -> 91934720.0

Revision                                       Result                  N
android-chrome@ca1c4e48aa                      86316373 +- 303653      6      good
android-chrome@2158fc5105                      87217493 +- 751473      6      good
android-chrome@2158fc5105,chromium@566949      87280981 +- 580341      6      good
android-chrome@2158fc5105,chromium@566970      86783317 +- 914950      6      good
android-chrome@2158fc5105,chromium@566971      91340800 +- 664275      6      bad       <--
android-chrome@2158fc5105,chromium@566972      91776341 +- 437100      6      bad
android-chrome@2158fc5105,chromium@566973      91519659 +- 619863      6      bad
android-chrome@2158fc5105,chromium@566975      91467776 +- 974951      6      bad
android-chrome@2158fc5105,chromium@566980      90930517 +- 452050      6      bad
android-chrome@2158fc5105,chromium@566991      91642539 +- 859284      6      bad
android-chrome@f6b5646c5d                      92066475 +- 741941      6      bad
android-chrome@adcd19c5ad                      91934720 +- 525273      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.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/8943706236213517072


For feedback, file a bug with component Speed>Bisection

 Issue 853005  has been merged into this issue.

 Issue 853007  has been merged into this issue.

Issue 852840 has been merged into this issue.

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

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

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: ca1c4e48aa84623f6f0c62214bdc831cc324f791
  bad_revision : f6b5646c5dfcbdc2dd9bea0a5262039a148fe621

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


Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_media/browse_media_youtube
  Change       : 14.23% | 13547861.3333 -> 15476053.3333

Revision                       Result                   N
android-chrome@ca1c4e48aa      13547861 +- 1066063      6      good
android-chrome@f6b5646c5d      15679943 +- 769254       9      bad
android-chrome@adcd19c5ad      15476053 +- 590067       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=browse.media.youtube 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/8943008766676657344


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Sadrul Habib Chowdhury
  Commit : 3821fdf5c54add24d02adef248a311c293ea0bd0
  Date   : Wed Jun 13 19:50:51 2018
  Subject: presentation feedback: Use a GLFence fallback.

Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/load_tools/load_tools_drive
  Change       : 11.32% | 16453290.6667 -> 18315946.6667

Revision                                       Result                   N
android-chrome@ca1c4e48aa                      16453291 +- 573242       6      good
android-chrome@2158fc5105                      16437248 +- 722681       6      good
android-chrome@2158fc5105,chromium@566949      16349867 +- 903034       6      good
android-chrome@2158fc5105,chromium@566955      16496981 +- 317931       6      good
android-chrome@2158fc5105,chromium@566957      16584363 +- 342011       6      good
android-chrome@2158fc5105,chromium@566958      18680036 +- 1202089      9      bad       <--
android-chrome@2158fc5105,chromium@566960      18370332 +- 941261       9      bad
android-chrome@2158fc5105,chromium@566970      18982002 +- 1232690      9      bad
android-chrome@2158fc5105,chromium@566991      19102379 +- 385866       6      bad
android-chrome@f6b5646c5d                      18315947 +- 650976       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.tools.drive 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/8942744216928589056


For feedback, file a bug with component Speed>Bisection