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

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


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

chromium-rel-win7-x64-dual

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Zhenyao Mo
  Commit : 39d8a7f229e1330e72724895eb4730b7108e47a0
  Date   : Mon Oct 30 13:45:42 2017
  Subject: Revert "One step further into moving GPU feature decisions to GPU process"

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : media.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/video.html?src_garden2_10s.webm_seek
  Change       : 1.33% | 146298290.556 -> 148243235.5

Revision             Result                    N
chromium@512468      146298291 +- 384255       9      good
chromium@512478      146353788 +- 78539.8      6      good
chromium@512483      146331970 +- 265714       9      good
chromium@512484      146375534 +- 112225       9      good
chromium@512485      148443860 +- 2293332      9      bad       <--
chromium@512486      148386431 +- 2180989      9      bad
chromium@512488      148400837 +- 2208298      9      bad
chromium@512507      148243236 +- 2063533      6      bad

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=video.html.src.garden2.10s.webm.seek media.desktop

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

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


For feedback, file a bug with component Speed>Bisection