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

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


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

chromium-rel-mac11-air

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

=== Auto-CCing suspected CL author miu@chromium.org ===

Hi miu@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Yuri Wiitala
  Commit : d70094cd62f6ad2482f66734d61845ded77d58bb
  Date   : Fri Sep 01 23:22:29 2017
  Subject: Video Capture: Support for populating frames via writable Mojo shmem.

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : CastV2Performance_gpu_30fps_wifi/capture_duration
  Change       : 10.08% | 10.6860745 -> 11.763027

Revision             Result                   N
chromium@499275      10.6861 +- 0.76401       6      good
chromium@499324      10.5124 +- 0.145685      6      good
chromium@499330      10.4461 +- 0.139685      6      good
chromium@499333      10.4043 +- 0.171445      6      good
chromium@499335      10.4814 +- 0.194698      6      good
chromium@499336      11.7608 +- 0.44546       6      bad       <--
chromium@499348      11.6947 +- 0.106396      6      bad
chromium@499372      11.763 +- 0.57943        6      bad

To Run This Test
  ./src/out/Release/performance_browser_tests --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/8969255809728066992


For feedback, file a bug with component Speed>Bisection