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

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


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

chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
linux-release

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Alex Moshchuk
  Commit : 9cf0ac139cc65890b9e036f704040c8da332d6e3
  Date   : Wed Oct 25 21:26:19 2017
  Subject: Add field trial testing config for sign-in process isolation.

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_media/load_media_dailymotion
  Change       : 22.22% | 19210240.0 -> 23478272.0

Revision             Result                  N
chromium@511551      19210240 +- 642119      6      good
chromium@511581      19122859 +- 605396      6      good
chromium@511589      19297621 +- 605396      6      good
chromium@511593      19210240 +- 642119      6      good
chromium@511594      23478272 +- 642119      6      bad       <--
chromium@511595      23478272 +- 642119      6      bad
chromium@511596      23041365 +- 957215      6      bad
chromium@511611      23128747 +- 478607      6      bad
chromium@511670      23478272 +- 642119      6      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=load.media.dailymotion 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/8964327683802341968


For feedback, file a bug with component Speed>Bisection