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

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


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

chromium-rel-mac-hdd

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

 Issue 629296  has been merged into this issue.

Tentatively setting owner to waffles@, since bisect identified their change in duplicate  bug 629296 .

===== 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     Std Dev  N   Good?
chromium@405307  1445.45  28.4599  18  good
chromium@405390  1445.38  30.645   18  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 629262

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_hi_ru
Test Metric: warm_times/page_load_time
Relative Change: 0.47%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/649
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006763577818792944


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

| 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!

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

Strange that the bisect failed. Re-running on another of the alerts that had a very clear sharp jump...

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


===== SUSPECTED CL(s) =====
Subject : Fix component-installer-controlled Flash path.
Author  : waffles
Commit description:
  
BUG=627959

Review-Url: https://codereview.chromium.org/2150573004
Cr-Commit-Position: refs/heads/master@{#405419}
Commit  : 3436cd4cbccb4c573185e2faefc248727e1baecb
Date    : Thu Jul 14 02:50:17 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@405393  680.358  4.09377  5  good
chromium@405413  681.847  3.16145  5  good
chromium@405418  681.954  1.86989  5  good
chromium@405419  767.407  3.69075  5  bad    <--
chromium@405420  769.357  3.68616  5  bad
chromium@405421  768.099  1.896    5  bad
chromium@405423  768.776  1.96413  5  bad
chromium@405433  766.194  4.05904  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 629262

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_ar_fa_he
Test Metric: cold_times/page_load_time
Relative Change: 12.62%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/750
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006668101907655600


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

| 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!

(There must be something going on in that CL that is triggering this; discussion in the duplicate bug.)