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

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


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

android-nexus5
chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_social/browse_social_twitter

Revision             Result                  N
chromium@510109      19806316 +- 266837      21      good
chromium@510398      19794429 +- 348452      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.social.twitter 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/8964938938350037920


For feedback, file a bug with component Speed>Bisection

Bisect couldn't repro.