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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : media.desktop
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/video.html?src_smpte_3840x2160_60fps_vp9.webm_seek

Revision             Result                    N
chromium@515392      371112927 +- 3575297      21      good
chromium@515490      371223753 +- 4144716      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.smpte.3840x2160.60fps.vp9.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/8963093421900760336


For feedback, file a bug with component Speed>Bisection