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

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


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

perf-monochrome-o-phone

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

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: monochrome-phone-perf-bisect
  Benchmark    : memory.dual_browser_test
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/on_webview/google_1600_amphitheatre_pkwy_mountain_view_ca


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=google.1600.amphitheatre.pkwy.mountain.view.ca 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/8945072740859412320


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: monochrome-phone-perf-bisect
  Benchmark    : memory.dual_browser_test
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/on_webview/google_1600_amphitheatre_pkwy_mountain_view_ca


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=google.1600.amphitheatre.pkwy.mountain.view.ca 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/8945072699395018608


For feedback, file a bug with component Speed>Bisection

Simon, Juan, any ideas what's happening here?

I think this might be the same issue as  crbug.com/848001 , the alerts are nearly the same range (and arguably the ones in this alert should be nudged forward).

This test seems to be crashing and not producing any values.

This seems to be the cause of the problem:

	05-30 20:37:03.101  7889  7889 E AndroidRuntime: Caused by: java.lang.UnsatisfiedLinkError: dlopen failed: "/data/app/com.google.android.apps.chrome-1/base.apk!/lib/armeabi-v7a/libmonochrome.so" is 32-bit instead of 64-bit
	05-30 20:37:03.101  7889  7889 E AndroidRuntime: 	at java.lang.Runtime.loadLibrary0(Runtime.java:977)
	05-30 20:37:03.101  7889  7889 E AndroidRuntime: 	at java.lang.System.loadLibrary(System.java:1530)
	05-30 20:37:03.101  7889  7889 E AndroidRuntime: 	at org.chromium.base.library_loader.LibraryLoader.c(SourceFile:74)
	05-30 20:37:03.101  7889  7889 E AndroidRuntime: 	... 31 more

From where is monochrome-phone-perf-bisect picking up builds?

Looks like gs://clankium-builds/arm-builder-rel/*

Yeah, that's the issue, it should be from: gs://clankium-builds/arm64-builder-rel/*

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave/+/f00aa96d2eccabb10315c1a34732cbca6ad006f0

commit f00aa96d2eccabb10315c1a34732cbca6ad006f0
Author: Simon <simonhatch@chromium.org>
Date: Wed Jun 06 16:12:38 2018

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

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

Bisect Details
  Configuration: monochrome-phone-perf-bisect
  Benchmark    : memory.dual_browser_test
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/on_webview/google_1600_amphitheatre_pkwy_mountain_view_ca
  Change       : 0.13% | 30934528.7619 -> 30894758.4762

Revision                       Result                  N
android-chrome@b21f397820      30934529 +- 200336      21      good
android-chrome@48b68a3310      30894758 +- 237994      21      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=google.1600.amphitheatre.pkwy.mountain.view.ca 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/8944442517866707280


For feedback, file a bug with component Speed>Bisection

Well, the regression didn't reproduce, but now bisect on this bot does work which is a nice thing. Thanks Simon!

heh, baby steps