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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgu875twoM


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

chromium-rel-win10

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

===== BISECT JOB RESULTS =====
Status: failed


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N     Good?
chromium@434072  16.9154  231.18   1474  good
chromium@434117  17.0507  258.033  1463  bad

Bisect job ran on: winx64_10_perf_bisect
Bug ID: 669232

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests smoothness.image_decoding_cases
Test Metric: frame_times/frame_times
Relative Change: None

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64_10_perf_bisect/builds/786
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994711002644267840


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6425925376278528

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

Assigning to benchmark owner in case they can help find bad CLs. There isn't really a clear CL range that caused this regression.

This was pretty noisy and has since recovered.