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

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


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

perf-go-phone-1024

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

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

Hi yiyix@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 : yiyix
  Commit : 6a4ede3e8b19101ba5b1735e0a2178b9541a21a3
  Date   : Mon May 14 10:38:30 2018
  Subject: Fix Regression: Black patch is seen while opening new page

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/load_news/load_news_washingtonpost
  Change       : 29.12% | 652740.0 -> 842820.0

Revision                                       Result             N
android-chrome@4426288b2b                      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558065      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558164      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558213      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558238      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558250      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558252      652740 +- 0.0      6      good
android-chrome@4426288b2b,chromium@558253      842820 +- 0.0      6      bad       <--
android-chrome@4426288b2b,chromium@558256      842820 +- 0.0      6      bad
android-chrome@4426288b2b,chromium@558262      842820 +- 0.0      6      bad
android-chrome@dda312c828                      842820 +- 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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.washingtonpost 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/8946257907952690384


For feedback, file a bug with component Speed>Bisection

 Issue 844124  has been merged into this issue.

Issue 845168 has been merged into this issue.

https://chromium.googlesource.com/chromium/src.git/+/be2578711ee47f8b8a5ba8b15108dedb50a27367

 Issue 846060  has been merged into this issue.

 Issue 846342  has been merged into this issue.