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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science

Revision             Result                   N
chromium@484288      94293935 +- 2998119      21      good
chromium@484349      94475914 +- 4658574      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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science

Revision             Result                   N
chromium@484288      91402304 +- 3829558      21      good
chromium@484349      91489198 +- 2401588      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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : perezju
  Commit : b5c1738572410f30cbcae23354f1738cf0b222ef
  Date   : Wed Jul 05 08:52:52 2017
  Subject: [Telemetry] Trigger GC on Chrome processes forked from Zygote

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_www_baidu_com_s_word_google
  Change       : 1.86% | 93273612.0 -> 95010486.6667

Revision                                 Result                   N
chromium@484235                          93273612 +- 1514761      6      good
chromium@484239                          93303649 +- 1167942      6      good
chromium@484239,catapult@b5c1738572      95215969 +- 1281320      6      bad       <--
chromium@484240                          95207948 +- 1407664      6      bad
chromium@484241                          95306764 +- 1192451      6      bad
chromium@484243                          95041889 +- 1336129      6      bad
chromium@484251                          95213751 +- 983413       6      bad
chromium@484266                          95143436 +- 1766340      6      bad
chromium@484297                          95010487 +- 1545382      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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection