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

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


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

chromium-rel-win7-gpu-intel
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_fast/capture_duration

Revision             Result                   N
chromium@502441      12.5626 +- 0.179818      21      good
chromium@502445      12.7789 +- 3.73248       21      unknown
chromium@502448      12.6148 +- 0.288653      21      bad
chromium@502454      12.6102 +- 0.163617      14      bad
chromium@502466      12.6361 +- 0.227012      9       bad
chromium@502491      12.7863 +- 3.80613       21      bad

To Run This Test
  .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.