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

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


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

health-plan-clankium-phone
health-plan-webview-low-end-phone
health-plan-webview-phone
perf-go-phone-1024
perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 9736c5256c12c84980720228edf0f09614210ae5
  bad_revision : a929e4d34e2b558db9e5cb11b32e764a81acef18

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: webview-low-end-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html
  Change       : 6.58% | 11851197.1429 -> 12638409.3333

Revision                                       Result                  N
android-chrome@be902aa047                      11851197 +- 291205      14       good
android-chrome@be902aa047,chromium@556849      11988047 +- 254594      14       good
android-chrome@be902aa047,chromium@556890      11944162 +- 291692      14       good
android-chrome@be902aa047,chromium@556900      ---                     ---      build failure
android-chrome@be902aa047,chromium@556901      12461656 +- 359090      9        bad
android-chrome@be902aa047,chromium@556910      12466694 +- 342782      14       bad
android-chrome@1390428f76                      12442850 +- 362546      14       bad
android-chrome@41db54dacb                      12638409 +- 392817      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.m.intl.taobao.com.group.purchase.html 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/8946904132694578240


For feedback, file a bug with component Speed>Bisection

That brings down the regression to the range:
http://test-results.appspot.com/revision_range?start=556890&end=556901&n=1000

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

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

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

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 0.99% | 29027553.7143 -> 29314273.7143

Revision                       Result                  N
android-chrome@be902aa047      29027554 +- 301450      21      good
android-chrome@1390428f76      29314274 +- 352066      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.www.amazon.com.gp.aw.s.k.nexus 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/8946456984104452928


For feedback, file a bug with component Speed>Bisection

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

Suspected Commit
  Author : jgruber
  Commit : e0c3f6d6ca005185e537fb85bbe841fe5dae5240
  Date   : Tue May 08 11:21:37 2018
  Subject: Disable embedded builtins

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_footprint_size_avg/load_news/load_news_washingtonpost
  Change       : 0.69% | 134784341.333 -> 135718912.0

Revision                                                     Result                   N
android-chrome@be902aa047                                    134784341 +- 320177      6      good
android-chrome@be902aa047,chromium@556849                    134853063 +- 236475      9      good
android-chrome@be902aa047,chromium@556890                    134999154 +- 319952      9      good
android-chrome@be902aa047,chromium@556893                    134858752 +- 270581      6      good
android-chrome@be902aa047,chromium@556894                    134813696 +- 237409      6      good
android-chrome@be902aa047,chromium@556894,v8@855850eb7f      134875364 +- 402988      9      good
android-chrome@be902aa047,chromium@556894,v8@e0c3f6d6ca      135892309 +- 210766      6      bad       <--
android-chrome@be902aa047,chromium@556894,v8@c34562803e      135739392 +- 444779      6      bad
android-chrome@be902aa047,chromium@556894,v8@9f5018c9b0      135834283 +- 280433      6      bad
android-chrome@be902aa047,chromium@556894,v8@61af2762ef      135731883 +- 220221      6      bad
android-chrome@be902aa047,chromium@556895                    135642453 +- 238828      6      bad
android-chrome@be902aa047,chromium@556901                    135785813 +- 356888      6      bad
android-chrome@be902aa047,chromium@556911                    135752363 +- 258102      6      bad
android-chrome@1390428f76                                    135590798 +- 268591      9      bad
android-chrome@41db54dacb                                    135718912 +- 252558      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=load.news.washingtonpost 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/8946457035630203392


For feedback, file a bug with component Speed>Bisection