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

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


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

perf-monochrome-n-phone

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

=== 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: monochrome-phone-perf-bisect
  Benchmark    : memory.dual_browser_test
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/on_chrome/http_m_intl_taobao_com_group_purchase_html
  Change       : 24.11% | 1451945.71429 -> 1801984.0

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


Revision                       Result                  N
android-chrome@74662f91c8      1451946 +- 12.6213      14       good
android-chrome@1032e70048      ---                     ---      build failure
android-chrome@4e67b217c5      ---                     ---      build failure
android-chrome@bdf6ddc146      1801984 +- 19.533       14       bad

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.intl.taobao.com.group.purchase.html memory.dual_browser_test

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940539641569466016


For feedback, file a bug with component Speed>Bisection

Manually duping as 

  46a78fb Revert "[embedded-builtins] Enable on all arches except x86 for benchmarks" by Sigurd Schneider

is in the roll and the symptoms fit.