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

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


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

chromium-rel-win7-gpu-ati

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : v8-gc-scavenger_max/browse_media/browse_media_pinterest
  Change       : 49.34% | 4.37704761905 -> 6.53664285714

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/3373ef06dbe342b74832f7285bf410cf9978cfe4..e38bd1e31c4c1394bae7ba113b23b1315e3be861


Revision             Result                  N
chromium@492258      4.37705 +- 7.68978      21       good
chromium@492268      4.36079 +- 6.30887      14       good
chromium@492275      4.03479 +- 4.1399       14       good
chromium@492277      4.0951 +- 7.35598       21       good
chromium@492278      ---                     ---      build failure
chromium@492279      6.1845 +- 7.21564       14       bad
chromium@492302      6.53664 +- 7.13083      14       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/8971563567079002128


For feedback, file a bug with component Speed>Bisection

Closing due to flaky benchmark.