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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=53efb66336d1ba7a2b94e3caa9a30e45cfd08299bd90ea1c54ae3fdfe90c9cc9


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

chromium-rel-mac11

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : v8-gc-latency-mark-compactor_max/v8-gc-latency-mark-compactor_max

Revision             Result                  N
chromium@494122      5.708 +- 1.23127        6      good
chromium@495457      13.1545 +- 1.92066      6      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 memory.long_running_idle_gmail_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8969997817645838576


For feedback, file a bug with component Speed>Bisection

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

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

Trying a few more bisects.

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : v8-gc-latency-mark-compactor_max/v8-gc-latency-mark-compactor_max

Revision             Result                  N
chromium@495450      11.8441 +- 10.4878      21      good
chromium@495510      11.8599 +- 9.18384      21      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 memory.long_running_idle_gmail_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966182151704342480


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : v8-gc-latency-mark-compactor_avg/v8-gc-latency-mark-compactor_avg

Revision             Result                   N
chromium@494122      5.02861 +- 0.439016      6      good
chromium@495457      9.17461 +- 2.32656       6      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 memory.long_running_idle_gmail_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966182146496286640


For feedback, file a bug with component Speed>Bisection

+simonhatch, any ideas what's wrong with the bisect in #8? I'm going to try re-rerunning one more time.

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

Think it's hitting the 1 hr no output limit and getting killed. Some thoughts on this:

1. It's alerting on the summary metric I believe, rather than the individual pages, not a big deal but just noticed there's no story filter.

2. It's also happening on mac pro, so I'll kick a Pinpoint job.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/149321b9780000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/149321b9780000

Not sure if there's much else we can do here? Really noisy test, can't narrow it down.

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : memory.long_running_idle_gmail_tbmv2
  Metric       : v8-gc-latency-mark-compactor_avg/v8-gc-latency-mark-compactor_avg

Revision             Result                   N
chromium@494122      4.74489 +- 0.405148      6      good
chromium@495457      8.69164 +- 1.21266       6      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 memory.long_running_idle_gmail_tbmv2

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8966106945232767216


For feedback, file a bug with component Speed>Bisection

Bisect unable to find culprit, this regression exists in stable. Ignoring.