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

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


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

android-nexus7v2
chromium-rel-mac11-air
chromium-rel-win7-x64-dual
linux-release

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : Total:duration_avg/browse_media/browse_media_pinterest

Revision             Result                  N
chromium@499562      6594.2 +- 1000.03       21      good
chromium@499596      6541.11 +- 602.277      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/8969125476690221312


For feedback, file a bug with component Speed>Bisection