Fix strict mode violation on document mode initialization.

chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/DocumentTabModelImpl.java

Index: chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/DocumentTabModelImpl.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/DocumentTabModelImpl.java b/chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/DocumentTabModelImpl.java
index e44979e2b068e2221300f2af508cc7b53a7277e9..96fc1659709061069540f402bdc1f92aece5945b 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/DocumentTabModelImpl.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/DocumentTabModelImpl.java
@@ -136,6 +136,14 @@ public class DocumentTabModelImpl extends TabModelJniBridge implements DocumentT
     private int mLastShownTabId = Tab.INVALID_TAB_ID;
 
     /**
+     * Pre-load shared prefs to avoid being blocked on the
+     * disk access async task in the future.
+     */
+    public static void warmUpSharedPrefs(Context context) {

[hartmanng, 2015/11/26 21:51:13]

As an alternative to the public static method here, we could just call

mApplication.getSharedPreferences(DocumentTabModelImpl.PREF_PACKAGE,
Context.MODE_PRIVATE);

from ChromeBrowserInitializer.warmUpSharedPrefs(), and remove the
@VisibleForTesting annotation from PREF_PACKAGE.

+        context.getSharedPreferences(PREF_PACKAGE, Context.MODE_PRIVATE);
+    }
+
+    /**
      * Construct a DocumentTabModel.
      * @param activityDelegate Delegate to use for accessing the ActivityManager.
      * @param storageDelegate Delegate to use for accessing persistent storage.