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

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


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

chromium-rel-mac12

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 2d85a12f776d580fd9d2f12da4a8a94ee81d3245
  bad_revision : 16b181b38687ea4dddf97a0761f773751ee2826b

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


Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/AllRecipes

Revision             Result                  N
chromium@496588      388.914 +- 107.51       6      good
chromium@496600      421.624 +- 66.1025      6      good
chromium@496606      402.25 +- 111.744       6      good
chromium@496608      946.346 +- 307.361      6      bad
chromium@496609      763.85 +- 632.461       9      bad
chromium@496612      1001.78 +- 273.987      6      bad
chromium@496636      944.812 +- 611.432      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 --story-filter=AllRecipes loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

Re-kicking (maybe bisect got interrupted?) but 99% sure this is r496607

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Pavel Feldman
  Commit : 9ce7836fdec98fde42fc61347c4161077dbea0fc
  Date   : Wed Aug 23 07:07:21 2017
  Subject: DevTools: introduce lifecycle events reported over the page domain.

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : loading.desktop
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/pcv1-warm/AllRecipes
  Change       : 129.54% | 417.227666667 -> 957.6965

Revision             Result                  N
chromium@496606      417.228 +- 69.6896      6      good
chromium@496607      843.479 +- 313.032      6      bad       <--
chromium@496608      957.697 +- 219.796      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 --story-filter=AllRecipes loading.desktop

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

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


For feedback, file a bug with component Speed>Bisection