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

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


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

chromium-rel-mac-retina

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

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/uol.com.br

Revision             Result                  N
chromium@500490      150.554 +- 99.4447      21      good
chromium@500532      151.457 +- 90.4572      20      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=uol.com.br loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-cold/uol.com.br
  Change       : 17.30% | 138.107428571 -> 161.995785714

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/f144ed8ee752b61f0607e458ba1a6427219c021b..512536e0e8a47f4ba78613296cd9a8ce2d805b3d


Revision             Result                  N
chromium@500264      138.107 +- 13.8555      21       good
chromium@500297      138.605 +- 10.2261      21       good
chromium@500313      138.123 +- 8.38043      14       good
chromium@500321      137.91 +- 6.07586       9        good
chromium@500325      138.44 +- 8.0819        14       good
chromium@500327      137.895 +- 10.4069      14       good
chromium@500328      138.891 +- 8.12749      14       good
chromium@500329      ---                     ---      build failure
chromium@500330      ---                     ---      build failure
chromium@500331      140.754 +- 7.66995      14       bad
chromium@500402      163.029 +- 82.7794      14       bad
chromium@500532      161.996 +- 82.4996      14       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=uol.com.br loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

This came back down.