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

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


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

chromium-rel-win7-gpu-nvidia

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

=== 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:gpu:effective_size_avg/video.html?src_tulip2.m4a_type_audio

Revision             Result                  N
chromium@506086      8314790 +- 2377947      21      good
chromium@506173      8364722 +- 2399864      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.tulip2.m4a.type.audio 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/8966188087272188416


For feedback, file a bug with component Speed>Bisection

I will see if we can figure out what caused this to go up. May need pinpoint because it is flaky.

dtu, is there any way I could try pinpoint for this?