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

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


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

chromium-rel-mac11-pro

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

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

Bisect Details
  Configuration: mac_pro_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:gpu_process:reported_by_os:system_memory:native_heap:private_dirty_size_avg/video.html?src_garden2_10s.mp4

Revision             Result                   N
chromium@482524      17300368 +- 7779337      21      good
chromium@482583      16984597 +- 6124280      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.garden2.10s.mp4 media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

Bisect didn't find a culprit, and now the bug is stale.