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

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


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

chromium-rel-win10

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

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

Hi geofflang@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 : Geoff Lang
  Commit : 65d1cd6e7454a3fd383d0deeaaad67918f97be3b
  Date   : Tue Jul 25 17:34:04 2017
  Subject: Revert "Lazily create shader translators and implement glReleaseShaderCompiler"

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_news/load_news_qq
  Change       : 2.26% | 27486019.0 -> 28107612.3333

Revision             Result                   N
chromium@489334      27486019 +- 235300       6      good
chromium@489346      27405290 +- 75012.5      6      good
chromium@489352      27445401 +- 91224.8      6      good
chromium@489353      27437266 +- 112316       6      good
chromium@489354      28053624 +- 77833.1      6      bad       <--
chromium@489355      28129082 +- 154684       6      bad
chromium@489358      28148510 +- 223046       6      bad
chromium@489382      28053829 +- 83539.1      6      bad
chromium@489429      28107612 +- 127033       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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.qq system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972808813843107280


For feedback, file a bug with component Speed>Bisection

 Issue 750281  has been merged into this issue.

This is from a revert, so wontfix.