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

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


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

chromium-rel-win7-dual

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

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

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

Revision             Result                  N
chromium@491362      701.326 +- 335.046      21      good
chromium@491456      733.123 +- 422.455      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.flickr.infinite.scroll 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/8971854150619328720


For feedback, file a bug with component Speed>Bisection

The same regression is seen is ref.