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

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


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

health-plan-clankium-phone

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

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

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/https_m_facebook_com_rihanna
  Change       : 3.11% | 70901369.9048 -> 73104627.8095

Revision                       Result                   N
android-chrome@9c123ef27e      70901370 +- 3920427      21      good
android-chrome@a3dc2608ce      73104628 +- 224076       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=https.m.facebook.com.rihanna 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/8945183006539370352


For feedback, file a bug with component Speed>Bisection

Downgrading P2 issues unmodified for more than 6 months, which have no owner or component.