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

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


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

android-nexus7v2

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

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

Suspected Commit
  Author : tzik
  Commit : 211d6bc6aacfeed4aa730418801c86c7cef6719c
  Date   : Thu Jun 29 04:19:13 2017
  Subject: Notify RendererScheduler of starting LOADING phase on DidStartProvisionalLoad

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_media/browse_media_facebook_photos
  Change       : 59.48% | 36.129 -> 57.617

Revision             Result                  N
chromium@483015      36.129 +- 43.5921       8      good
chromium@483166      34.7898 +- 17.5859      5      good
chromium@483242      26.9468 +- 21.9954      6      good
chromium@483280      35.3797 +- 26.6319      6      good
chromium@483290      23.7474 +- 24.9503      7      good
chromium@483293      31.0633 +- 45.8372      8      good
chromium@483294      28.284 +- 34.6621       5      good
chromium@483295      58.3932 +- 10.8475      9      bad       <--
chromium@483299      60.9543 +- 7.63731      6      bad
chromium@483317      57.617 +- 13.0484       9      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection