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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/video.html?src_crowd2160.mp4

Revision             Result                     N
chromium@487871      355471738 +- 780606        21      good
chromium@488015      356080750 +- 12102866      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.crowd2160.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/8973077113884438624


For feedback, file a bug with component Speed>Bisection

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