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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnvm2xAgM


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao

Revision             Result                 N
chromium@482283      4161392 +- 256844      21      good
chromium@482424      4170792 +- 111374      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.search.taobao 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/8975101609501367920


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao

Revision             Result                  N
chromium@482283      4147353 +- 116487       21      good
chromium@482424      4171272 +- 75964.5      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.search.taobao 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/8975094069743142928


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_search/load_search_taobao
  Change       : 0.44% | 4147776.28571 -> 4166018.57143

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/239b2102228fabe30cd9568d9c2ab5ef04f69d7a..3aeae9f58d9507abd2ecef33041fc2685eb79613


Revision             Result                  N
chromium@482283      4147776 +- 190200       14       good
chromium@482321      4139879 +- 95713.6      9        good
chromium@482340      4141265 +- 104138       14       good
chromium@482343      4139179 +- 62320.2      14       good
chromium@482344      ---                     ---      build failure
chromium@482345      ---                     ---      build failure
chromium@482346      4175002 +- 108166       14       bad
chromium@482350      4173663 +- 66963.1      14       bad
chromium@482359      4166107 +- 48216.9      14       bad
chromium@482435      4165967 +- 48504.9      14       bad
chromium@482587      4166019 +- 48185.8      14       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.search.taobao 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/8975096966873093840


For feedback, file a bug with component Speed>Bisection

Suspecting 

acf4929 [heap] Replace concurrent marking deque with work-stealing worklist. by Ulan Degenbaev · 8 days ago

as the only gc-related CL in the range.

system_health samples memory usage after GC. My CL can only affect memory usage during GC. So pretty sure it is not my CL.

Closing since bisect is failing and the regression is small compared to noise level.