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

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


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

chromium-rel-mac12
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win8-dual

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

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

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : V8 C++:duration_avg/browse_media/browse_media_tumblr

Revision             Result                  N
chromium@501846      227.173 +- 22.7412      21      good
chromium@501931      225.708 +- 20.4887      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.tumblr 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/8967203098367634688


For feedback, file a bug with component Speed>Bisection