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

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


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

android-nexus5X

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_m_youtube_com_results_q_science

Revision             Result                   N
chromium@498063      41653003 +- 1165010      21      good
chromium@498098      41865898 +- 1211205      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/8969252394033567504


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Timothy Loh
  Commit : 2db3fa641f2b6a05ee894f158a93a419caf3e896
  Date   : Tue Aug 29 03:09:33 2017
  Subject: Prepare tests for enabling modal permission prompts and remove gesture experiment

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_m_youtube_com_results_q_science
  Change       : 1.65% | 40823628.4444 -> 41481377.7778

Revision             Result                   N
chromium@497830      40823628 +- 692844       9       good
chromium@497965      40725097 +- 507764       9       good
chromium@497999      40943957 +- 1714563      14      good
chromium@498002      40864645 +- 740006       6       good
chromium@498003      40736304 +- 457525       6       good
chromium@498004      41618480 +- 525107       6       bad       <--
chromium@498008      41666153 +- 1379398      9       bad
chromium@498016      41599365 +- 678735       6       bad
chromium@498032      41606420 +- 798478       9       bad
chromium@498099      41316912 +- 1069348      14      bad
chromium@498367      41481378 +- 452271       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 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/8969179160247880000


For feedback, file a bug with component Speed>Bisection