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

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


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

health-plan-clankium-phone

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

This is most likely:
https://chrome-internal.googlesource.com/clank/internal/apps/+/dfb58c04e51c2e3eb18f7e78fcc829b7d9d6ff05

=== Auto-CCing suspected CL author agrieve@chromium.org ===

Hi agrieve@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Andrew Grieve
  Commit : dfb58c04e51c2e3eb18f7e78fcc829b7d9d6ff05
  Date   : Fri May 11 03:48:36 2018
  Subject: Revert "Remove -stablesparsenaming proguard flag"

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 2.62% | 90420054.6667 -> 92786348.0

Revision                       Result                  N
android-chrome@a03058257f      90420055 +- 237365      6      good
android-chrome@159f504c2c      90127361 +- 270453      6      good
android-chrome@e65cccf457      91015511 +- 138990      6      good
android-chrome@6b1376335e      90944684 +- 302386      6      good
android-chrome@dfb58c04e5      92824748 +- 167294      6      bad       <--
android-chrome@1bfcb4ee3d      92855127 +- 176407      6      bad
android-chrome@120ca38372      92786348 +- 156888      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.search.yahoo.com.search..ylt.p.google 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/8946538136272697648


For feedback, file a bug with component Speed>Bisection

Just confirming, known regression. :)

 Issue 842761  has been merged into this issue.