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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3on4qgkM


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

chromium-rel-win7-gpu-nvidia

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

=== 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: winx64nvidia_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_media/browse_media_imgur
  Change       : 4.55% | 82082476.2431 -> 82093704.1508

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/716a39de127774035bcba8fec1b9c4cd93f629d5..6614832e3a90564cb4e24c02eea867a9666b3ca0


Revision             Result                    N
chromium@483905      82082476 +- 9068869       14       good
chromium@483906      ---                       ---      build failure
chromium@483907      ---                       ---      build failure
chromium@483908      82093704 +- 13449253      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.imgur v8.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8975105280135881040


For feedback, file a bug with component Speed>Bisection

allocated_objects_size_avg has recovered in the meantime.