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

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


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

chromium-rel-mac11
chromium-rel-mac11-air

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/Colorado.edu

Revision             Result                  N
chromium@497683      394.353 +- 78.9237      21      good
chromium@497698      382.109 +- 62.056       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 --story-filter=Colorado.edu loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

Bisect can't repro, no ref build, maybe a bot issue?