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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxa-UtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxfLktwoM


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

chromium-rel-mac-retina

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

===== 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@418714  44.6715  3.13422  18  good
chromium@418748  44.9525  2.8961   18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 649982

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total_outside_idle/v8_gc_total_outside_idle
Relative Change: 6.55%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1684
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9000579637054450624


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

| 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/8999843500852508704

===== 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@418714  45.3535  3.48495  18  good
chromium@418748  45.8868  2.91985  18  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 649982

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests v8.top_25_smooth
Test Metric: v8_gc_total_outside_idle/v8_gc_total_outside_idle
Relative Change: 6.06%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1713
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999843500852508704


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

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

https://chromeperf.appspot.com/buildbucket_job_status/8999803945449753760

perf sheriff fixit: Clearing owners for sheriff bugs where the sheriff is the owner, to clarify that the rotation is responsible for triage.

Looks like there were two regressions, the one this bug concerns recovered by 422974.