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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAn4alpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAn6nipgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAn7ecpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAn-SzvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDA3-ShpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAn6m2twoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDAn-3VrwoM


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

chromium-rel-win7-dual

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision                Mean Value  Std. Dev.   Num Values  Good?
chromium@378220         35.773157   0.24488     12          good
chromium@378247         35.678983   0.102632    18          bad

Bisect job ran on: win_perf_bisect
Bug ID: 591085

Test Command: .\src\out\Release\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu
Test Metric: TabCapturePerformance_comp_gpu_novsync/Capture
Relative Change: 0.63%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6356
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9019374251047836048


| 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 label Cr-Tests-AutoBisect.  Thank you!

Alert has now recovered back down to previous levels now; it looks like it might be starting to spike up again in the most recent results; a separate bug should be filed for that. Meanwhile it's worth noting that the bisect job did not reproduce a regression.