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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-qWatwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghqzh7AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-r-kpgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-vWNoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-prvowsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-pGj5QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-oPRqgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-r2YqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg-uXJtAsM


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

android-nexus5
android-nexus7v2
android-one

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

=== 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 : 8785df15fe5a57651597d138d3c5aea0ffe3f661
  Date   : Wed May 24 16:04:45 2017
  Subject: Clear atlas textures at creation in Chrome

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 155.24% | 4728238.66667 -> 12068244.0

Revision                             Result                   N
chromium@474273                      4728239 +- 92.376        6      good
chromium@474336                      4728225 +- 73.0297       6      good
chromium@474344                      4728252 +- 97.9796       6      good
chromium@474348                      4728265 +- 92.376        6      good
chromium@474350                      4728239 +- 92.376        6      good
chromium@474350,skia@5458cf8ec6      4728212 +- 0.0           6      good
chromium@474350,skia@8785df15fe      12068284 +- 97.9796      6      bad       <--
chromium@474351                      12068271 +- 92.376       6      bad
chromium@474352                      12068284 +- 97.9796      6      bad
chromium@474368                      12068284 +- 97.9796      6      bad
chromium@474399                      12068244 +- 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-chromium --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/8978489453821656080

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


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

 Issue 726921  has been merged into this issue.

 Issue 726938  has been merged into this issue.

The implicated CL was reverted for a correctness regression.