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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/video.html?src_garden2_10s.webm

Revision             Result                   N
chromium@515392      37780172 +- 6418.65      21      good
chromium@515490      37780440 +- 8843.47      21      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 media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

No regression found.