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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghpjggwgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuSwtAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-s36hggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghrnmqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vyojgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuTzqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-u2BswsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuSwtAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqSEvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsbY6woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghsiEpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghuC0twsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-snQkQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-snQ4QsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-tfO-AkM


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

android-nexus5
android-nexus5X
android-webview-nexus5X

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

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

Hi bsalomon@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 : Brian Salomon
  Commit : 1c214313248a4b5a69af14539608c54fb67c2bf8
  Date   : Thu May 25 20:03:07 2017
  Subject: Revert "Clear atlas textures at creation in Chrome"

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 4.18% | 95840189.3333 -> 99846077.3333

Revision                             Result                    N
chromium@475215                      95840189 +- 1424380       6      good
chromium@475217                      91197373 +- 1915031       6      good
chromium@475218                      91527784 +- 1216846       6      good
chromium@475218,skia@9b51d1484a      92354493 +- 2037921       6      good
chromium@475218,skia@33fa454b16      92424808 +- 2017244       6      good
chromium@475218,skia@1c21431324      101757544 +- 1775719      6      bad       <--
chromium@475218,skia@fabe0b26d0      100904893 +- 1850517      6      bad
chromium@475218,skia@e7ba8b05d2      100618856 +- 1932722      6      bad
chromium@475218,skia@c020f17127      99613288 +- 2026612       6      bad
chromium@475219                      98848019 +- 1657151       6      bad
chromium@475222                      98668477 +- 2014444       6      bad
chromium@475229                      100188093 +- 4644356      6      bad
chromium@475242                      99846077 +- 6343604       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 memory.top_10_mobile_stress

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

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


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

This implicated CL was a revert of a recent CL. The revert was necessary to fix a correctness regression due to an Adreno GL driver bug.

 Issue 730209  has been merged into this issue.