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

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


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

android-one
android-webview-nexus5X

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

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

Hi hablich@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 : Michael Hablich
  Commit : 7b7658d8c800e8a42d2c0b5bc9bbe63155a69a22
  Date   : Wed Aug 02 08:28:01 2017
  Subject: Version 6.2.118.1 (cherry-pick)

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 5.95% | 5275581.33333 -> 5589696.66667

Revision                           Result                  N
chromium@491310                    5275581 +- 19388.7      6      good
chromium@491334                    5270777 +- 33166.1      6      good
chromium@491346                    5280099 +- 23842.2      6      good
chromium@491346,v8@7b7658d8c8      5556519 +- 215031       6      bad       <--
chromium@491347                    5502313 +- 297699       6      bad
chromium@491348                    5608093 +- 14083.5      6      bad
chromium@491349                    5568269 +- 212536       6      bad
chromium@491352                    5530441 +- 261046       6      bad
chromium@491358                    5589697 +- 89382.1      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-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/8972207422599867072


For feedback, file a bug with component Speed>Bisection

 Issue 752524  has been merged into this issue.

 Issue 755083  has been merged into this issue.

GC regressions are expected as tradeoff.

There are more memory improvements than regressions:  https://chromeperf.appspot.com/group_report?rev=491346