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

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


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

chromium-rel-mac12-mini-8gb

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

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

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

Revision             Result                   N
chromium@497582      26711906 +- 2115147      21      good
chromium@497652      26744650 +- 4759465      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/8969839615869033424


For feedback, file a bug with component Speed>Bisection