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

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


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

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

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

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

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_qq
  Change       : 0.80% | 26046582.4762 -> 26255478.4762

Revision                       Result                  N
android-chrome@74662f91c8      26046582 +- 264620      21      good
android-chrome@478583399d      26255478 +- 326093      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=browse.news.qq 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/8940543830653801280


For feedback, file a bug with component Speed>Bisection

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

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 0.56% | 26327357.5238 -> 26473838.2857

Revision                                       Result                   N
android-chrome@478583399d                      26327358 +- 204499       21       good
android-chrome@fdbeca77e3                      26296833 +- 113562       14       good
android-chrome@fdbeca77e3,chromium@575988      ---                      ---      build failure
android-chrome@fdbeca77e3,chromium@575989      26524551 +- 35203.4      6        bad
android-chrome@934b6671a2                      26461745 +- 142905       21       bad
android-chrome@5bcd964863                      26473838 +- 251266       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=http.m.youtube.com.results.q.science 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/8940472336304171136


For feedback, file a bug with component Speed>Bisection

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

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

Hi sigurds@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 : Sigurd Schneider
  Commit : 46a78fbedfcd458f5d35097bdf1a9947644f4b0e
  Date   : Tue Jul 17 15:33:20 2018
  Subject: Revert "[embedded-builtins] Enable on all arches except x86 for benchmarks"

Bisect Details
  Configuration: clankium-low-end-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_search_yahoo_com_search__ylt_p_google
  Change       : 2.18% | 22948060.0 -> 23448454.6667

Revision                                                     Result                   N
android-chrome@e5eafcf94f                                    22948060 +- 88600.6      6      good
android-chrome@74662f91c8                                    23038172 +- 78350.4      6      good
android-chrome@74662f91c8,chromium@575926                    23113265 +- 120659       6      good
android-chrome@74662f91c8,chromium@575929                    23103025 +- 107770       6      good
android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf      23493511 +- 106926       6      bad       <--
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      23492828 +- 104227       6      bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      23556316 +- 162359       6      bad
android-chrome@74662f91c8,chromium@575930                    23509895 +- 142542       6      bad
android-chrome@74662f91c8,chromium@575931                    23425244 +- 100898       6      bad
android-chrome@74662f91c8,chromium@575935                    23436167 +- 85278.2      6      bad
android-chrome@1032e70048                                    23448455 +- 147448       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/8940121227183889440


For feedback, file a bug with component Speed>Bisection