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

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


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

chromium-rel-win7-x64-dual

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@500482      26.0274 +- 51.2663      21      good
chromium@500532      19.808 +- 43.8469       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.pinterest v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@500482      25.8465 +- 59.3444      21      good
chromium@500532      24.6113 +- 41.0181      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.pinterest v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_avg/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@500482      7.66836 +- 14.5692      21      good
chromium@500532      7.74279 +- 17.201       21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.pinterest v8.runtimestats.browsing_desktop

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

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


For feedback, file a bug with component Speed>Bisection

The only CL in the range that looks like a possible culprit is

04419d4 [builtins] Migrate the Object constructor from JS to CSA. by Toon Verwaest · 6 days ago

https://chromium-review.googlesource.com/654900

Toon, FYI. I don't think this is actionable at the moment without a real bisect, but the bots are too flaky.