Android content_browsertests: Allow processing java tasks in nested mode.

content/public/android/java/src/org/chromium/content/browser/AndroidBrowserProcess.java

Index: content/public/android/java/src/org/chromium/content/browser/AndroidBrowserProcess.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/AndroidBrowserProcess.java b/content/public/android/java/src/org/chromium/content/browser/AndroidBrowserProcess.java
index 2219f8a65f00b9186c03d1df833915e057c42e39..823b4b239dcbf2ce117627e49d019e7535622f53 100644
--- a/content/public/android/java/src/org/chromium/content/browser/AndroidBrowserProcess.java
+++ b/content/public/android/java/src/org/chromium/content/browser/AndroidBrowserProcess.java
@@ -144,7 +144,11 @@ public class AndroidBrowserProcess {
     /**
      * Initialization needed for tests. Mainly used by content browsertests.
      */
-    public static void initChromiumBrowserProcessForTests() {
+    public static void initChromiumBrowserProcessForTests(Context context) {
+        ResourceExtractor resourceExtractor = ResourceExtractor.get(context);
+        resourceExtractor.startExtractingResources();
+        resourceExtractor.waitForCompletion();
+
         // Having a single renderer should be sufficient for tests.
         // We can't have more than MAX_RENDERERS_LIMIT.
         nativeSetCommandLineFlags(1 /* maxRenderers */);