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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/video.html?src_crowd1080.mp4

Revision             Result                   N
chromium@515392      88359289 +- 353911       21      good
chromium@515490      88443322 +- 1071771      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.crowd1080.mp4 media.desktop

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

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


For feedback, file a bug with component Speed>Bisection