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

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


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

android-nexus5
android-nexus6
android-nexus7v2
android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_tools/load_tools_drive

Revision             Result                   N
chromium@489985      24017098 +- 1012924      21      good
chromium@490179      24041851 +- 1190309      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 --story-filter=load.tools.drive system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Helen Li
  Commit : 73f7cac54a1108eac07d5c7c3367f979a899a0bd
  Date   : Thu Jul 27 14:57:57 2017
  Subject: [wpr-go] Switch system_health_mobile.json to use go

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/background_search/background_search_google
  Change       : 4.87% | 35729669.2222 -> 37517042.7778

Revision             Result                   N
chromium@489904      35729669 +- 385622       9       good
chromium@489918      35642850 +- 489856       6       good
chromium@489922      35780127 +- 607412       9       good
chromium@489923      37264566 +- 2084170      9       bad       <--
chromium@489924      37264208 +- 2766450      14      bad
chromium@489925      37288663 +- 974115       9       bad
chromium@489932      37191877 +- 1484139      6       bad
chromium@489959      36947317 +- 1552269      6       bad
chromium@490013      37035230 +- 1074689      6       bad
chromium@490121      37202261 +- 2540910      14      bad
chromium@490338      37517043 +- 516077       9       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 --story-filter=background.search.google system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection