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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : IC:duration_avg/browse_media/browse_media_tumblr

Revision             Result                  N
chromium@505793      245.11 +- 253.793       21      good
chromium@505895      268.403 +- 234.857      21      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=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/8966510174703730656


For feedback, file a bug with component Speed>Bisection