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

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


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

chromium-rel-mac-hdd

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

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


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

===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N   Good?
chromium@424370  30809205  33549848  30  good
chromium@424423  31870185  28225115  30  good
chromium@424450  36035843  37489443  30  unknown
chromium@424476  37874038  41488138  30  bad

Bisect job ran on: mac_hdd_perf_bisect
Bug ID: 675591

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2
Test Metric: memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg
Relative Change: 22.93%

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


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

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

+simonhatch bisect failed but states no clear reason.

Blocking on  crbug.com/665439  for the unclear output.

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: mac_hdd_perf_bisect
  Benchmark    : v8.infinite_scroll-ignition_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg

Revision             Result                    N
chromium@424370      30809205 +- 33549848      30      good
chromium@424423      31870185 +- 28225115      30      good
chromium@424450      36035843 +- 37489443      30      unknown
chromium@424476      37874038 +- 41488138      30      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests v8.infinite_scroll-ignition_tbmv2

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982659681031544224

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5031923653541888


| 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 Speed>Bisection.  Thank you!

chromium@424450 looks "bad", but maybe the metric is noisy?

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.