The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/908f3f7144b2598348d33a668d494f85070bba41

commit 908f3f7144b2598348d33a668d494f85070bba41
Author: Peter Wen <wnwen@chromium.org>
Date: Thu Sep 21 22:54:55 2017

Android: Patch flaky tests due to strict mode

Android system is crashing due to StrictMode but we need to know the
underlying cause in order to understand why it is flaking. Disabling
StrictMode just for those code paths as the flakiness is unreliable and
hard to reproduce.

BUG= 767423 , 767153 , 767624 

Change-Id: I0ddcabd876bab99841487742f039cea920ea433d
Reviewed-on: https://chromium-review.googlesource.com/677226
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: ccameron chromium <ccameron@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#503595}
[modify] https://crrev.com/908f3f7144b2598348d33a668d494f85070bba41/ui/android/java/src/org/chromium/ui/base/WindowAndroid.java

The cause of the StrictMode violation seems to be a Slog.wtf call in ActivityManagerService (https://android.googlesource.com/platform/frameworks/base/+/android-4.4.4_r2.0.1/services/java/com/android/server/am/ActiveServices.java#2081):

  // Sanity check: if the service listed for the app is not one
  // we actually are maintaining, just let it drop.
  if (smap.mServicesByName.get(sr.name) != sr) {
      ServiceRecord cur = smap.mServicesByName.get(sr.name);
      Slog.wtf(TAG, "Service " + sr + " in process " + app
              + " not same as in map: " + cur);
      continue;
  }

Slog.wtf would have caused a crash anyways, so I think this is a flake in Android that we can't really fix (even if we turn off StrictMode completely which I think loses much benefit). Hopefully we will migrate off Android 4 for testing in the coming years.

See Log.wtf in android code.