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

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


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

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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


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       : 1.44% | 25908513.1429 -> 26280664.0

Suspected Commit Range
  3 commits in range
  Unknown depot, please contact team to have this added.


Revision                       Result                  N
android-chrome@74662f91c8      25908513 +- 256744      14       good
android-chrome@1032e70048      ---                     ---      build failure
android-chrome@4e67b217c5      ---                     ---      build failure
android-chrome@bdf6ddc146      26180239 +- 269156      21       bad
android-chrome@478583399d      26280664 +- 252869      14       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/8940199267209704512


For feedback, file a bug with component Speed>Bisection

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

=== 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-phone-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_en_m_wikipedia_org_wiki_Science
  Change       : 1.46% | 41925500.5714 -> 42540120.0

Revision                                                     Result                  N
android-chrome@74662f91c8                                    41925501 +- 231043      14      good
android-chrome@74662f91c8,chromium@575926                    41908084 +- 290209      9       good
android-chrome@74662f91c8,chromium@575929                    41909043 +- 360858      14      good
android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf      42491992 +- 150368      6       bad       <--
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      42339985 +- 327833      9       bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      42329688 +- 304770      14      bad
android-chrome@74662f91c8,chromium@575930                    42473332 +- 141786      9       bad
android-chrome@74662f91c8,chromium@575931                    42635864 +- 138257      6       bad
android-chrome@74662f91c8,chromium@575935                    42498648 +- 264389      6       bad
android-chrome@1032e70048                                    42291483 +- 330457      21      bad
android-chrome@4e67b217c5                                    42459663 +- 339267      14      bad
android-chrome@22c1f49355                                    42540120 +- 109544      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.en.m.wikipedia.org.wiki.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/8940120746075176512


For feedback, file a bug with component Speed>Bisection