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

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


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

chromium-rel-mac-retina

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

=== 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_avg/v8-gc-latency-mark-compactor_avg

Revision             Result                  N
chromium@490310      4.35921 +- 1.43132      21      good
chromium@490379      4.37754 +- 1.84964      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/8972297755753056480


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, really noisy metric.