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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_max/browse_media/browse_media_imgur

Revision             Result                     N
chromium@490249      109806348 +- 32403414      21      good
chromium@490395      113251669 +- 51956562      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.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/8972264480137130816


For feedback, file a bug with component Speed>Bisection

Not reproducible.