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

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


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

chromium-rel-mac-retina
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win8-dual
linux-release

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14ac940af80000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/14ac940af80000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12e945e2f80000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/128668d2f80000

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

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/128668d2f80000

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/12e945e2f80000

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

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_social/browse_social_twitter_infinite_scroll

Revision             Result                   N
chromium@512013      25537797 +- 467088       21      good
chromium@512093      25315101 +- 4767757      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.social.twitter.infinite.scroll system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: win_x64_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/browse_tech/browse_tech_discourse_infinite_scroll

Revision             Result                  N
chromium@512007      30530397 +- 285426      20      good
chromium@512108      30517134 +- 238051      21      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.tech.discourse.infinite.scroll system_health.memory_desktop

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

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


For feedback, file a bug with component Speed>Bisection