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

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


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

chromium-rel-mac11
chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:new_space:allocated_objects_size_avg/browse_news/browse_news_reddit


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.news.reddit 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/8962666727746318032


For feedback, file a bug with component Speed>Bisection

Adding "Speed>Bisection" component because "Bisect failed for unknown reasons"

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

Retried on a smaller range, the recipe bisect timed out resolving the commits in the range since there's some ~16k commits in that range. Pinpoint also doesn't have this problem, and we're migrating to Win this/next week so we could try again there if we really want to bisect that enormous range.

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : v8.runtimestats.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:new_space:allocated_objects_size_avg/browse_news/browse_news_reddit


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.news.reddit 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/8962289656558628016


For feedback, file a bug with component Speed>Bisection

Hmm didn't realize that all the windows regressions were the same 16k or so range. Will need to wait until next week when we migrate Pinpoint.

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.