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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDguLq7qAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg2N6-ugsM


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : TabCapturePerformance_webrtc/CaptureSucceeded

Revision             Result                   N
chromium@449978      20.6482 +- 0.977635      21      good
chromium@450083      20.7069 +- 0.674213      21      bad

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

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8987514749423602544

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6334438004228096


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

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

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.