Turn on strict mode for all userdebug builds.

chrome/android/java/src/org/chromium/chrome/browser/init/ChromeBrowserInitializer.java

Index: chrome/android/java/src/org/chromium/chrome/browser/init/ChromeBrowserInitializer.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/init/ChromeBrowserInitializer.java b/chrome/android/java/src/org/chromium/chrome/browser/init/ChromeBrowserInitializer.java
index 99f7f9d31c7351035abd30dad1d63651863dd010..07cca2290869535b39c9931cd2a7d8dbed5a2f4e 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/init/ChromeBrowserInitializer.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/init/ChromeBrowserInitializer.java
@@ -254,7 +254,9 @@ public class ChromeBrowserInitializer {
 
     private static void configureStrictMode() {
         CommandLine commandLine = CommandLine.getInstance();
-        if ("eng".equals(Build.TYPE) || commandLine.hasSwitch(ChromeSwitches.STRICT_MODE)) {
+        if ("eng".equals(Build.TYPE)
+                || "userdebug".equals(Build.TYPE)

[jdduke (slow), 2015/06/01 21:34:58]

Ned, Annie: Can we somehow bypass this for telemetry perf tests? Perhaps when
the "--enable-gpu-benchmarking" flag is present? Or should we add a more
official flag for telemetry runs?

[nednguyen, 2015/06/01 21:37:53]

I would push back adding further flags to telemetry. What does this strict mode
do and why do we want to bypass this for telemetry per tests?

+                || commandLine.hasSwitch(ChromeSwitches.STRICT_MODE)) {
             StrictMode.enableDefaults();
             StrictMode.ThreadPolicy.Builder policy =
                     new StrictMode.ThreadPolicy.Builder(StrictMode.getThreadPolicy());