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

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


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

chromium-rel-mac11

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : startup.cold.blank_page
  Metric       : first_main_frame_load_time/first_main_frame_load_time


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

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

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


For feedback, file a bug with component Speed>Bisection

closing since this dropped down again.