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

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


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

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

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

=== 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: go-phone-512-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/load_media/load_media_facebook_photos
  Change       : 3.27% | 32840578.6667 -> 33915778.6667

Revision                                                     Result                  N
android-chrome@99b6fd7dae                                    32840579 +- 422279      6       good
android-chrome@6d62ea7763                                    33141407 +- 359174      9       good
android-chrome@e5eafcf94f                                    33092710 +- 272059      9       good
android-chrome@74662f91c8                                    33370328 +- 217608      14      good
android-chrome@74662f91c8,chromium@575928                    33230154 +- 310742      9       good
android-chrome@74662f91c8,chromium@575929                    33241987 +- 255828      9       good
android-chrome@74662f91c8,chromium@575929,v8@46a78fbedf      34124675 +- 138549      6       bad       <--
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      33898712 +- 242890      6       bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      33650676 +- 301126      9       bad
android-chrome@74662f91c8,chromium@575930                    33881645 +- 287403      6       bad
android-chrome@74662f91c8,chromium@575932                    33941037 +- 359031      9       bad
android-chrome@74662f91c8,chromium@575935                    33715855 +- 369303      14      bad
android-chrome@1032e70048                                    33712116 +- 281017      9       bad
android-chrome@478583399d                                    33801773 +- 221815      6       bad
android-chrome@029430f630                                    33915779 +- 422960      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.media.facebook.photos 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/8940071168035854032


For feedback, file a bug with component Speed>Bisection