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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7Mb4qgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrLnosQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrKTH9ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7PqZoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7LyV8AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrJnYpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrLfftwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7JDtvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MCwvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrNO95wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzMK6jAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrPj14ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrM3cqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7ISKuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrOfU5QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrO6evQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrMOeoAsM


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

android-nexus6
android-webview-nexus5X
android-webview-nexus6

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

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

Hi ericrk@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 : ericrk
  Commit : 42267f803ddaadca1d2d716a478ea5f8dd9f169f
  Date   : Fri Mar 24 18:39:52 2017
  Subject: Re-enable shader disk cache on Adreno 4/5xx

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/load_games/load_games_lazors
  Change       : 2.99% | 21451824.0 -> 22092860.0

Revision             Result                  N
chromium@459472      21451824 +- 170382      6      good
chromium@459480      21424659 +- 106880      6      good
chromium@459484      21391248 +- 177618      6      good
chromium@459486      21604399 +- 319573      6      good
chromium@459487      21635788 +- 184961      6      good
chromium@459488      21975979 +- 113723      6      bad       <--
chromium@459504      22092860 +- 190788      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=load.games.lazors system_health.memory_mobile

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

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


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

Explictly assigning. A CL you landed tripped one of the speed metrics we measure in the lab. If this is the first time this has happened to one of your CLs, or if it's been a while, please read: https://chromium.googlesource.com/chromium/src/+/master/docs/speed/addressing_performance_regressions.md

We're looking for one of the following:
1. Justification via explanation
2. Plan to revert or fix
3. Angry rage throwing of equipment at my head

Just be aware that I'm trained in trumpet playing and First Aid and am not afraid to use it.

Note: This was a bulk edit message and not very personal.

erickrk: anything we can do about this regression at this point?

Sorry, the change which caused this regression was reverted for other reasons. Closing this out.