Prefetch the native library from native code by parsing /proc/pid/maps.

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

Index: chrome/android/java/src/org/chromium/chrome/browser/init/NativeInitializationController.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/init/NativeInitializationController.java b/chrome/android/java/src/org/chromium/chrome/browser/init/NativeInitializationController.java
index 57f3e28af0ecff236f221d8efd23699cfdc31fcf..3f6ba4d08c78c3c8c506851f13da856b505256be 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/init/NativeInitializationController.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/init/NativeInitializationController.java
@@ -91,7 +91,7 @@ class NativeInitializationController {
                     //   generally startup on some devices, most likely by
                     //   competing for IO.
                     // For experimental results, see http://crbug.com/460438.
-                    libraryLoader.asyncPrefetchLibrariesToMemory(mContext);

[rmcilroy, 2015/03/24 15:18:26]

Can we delete asyncPrefetchLibrariesToMemory from the code now?

[Benoit L, 2015/03/25 10:36:19]

Can we keep it as a fallback for now, in case something goes wrong with the
fork()-based solution?

[rmcilroy, 2015/03/25 15:12:18]

Are you meaning fallback as in keep the code around incase we need it again or
actually fallback at runtime to the previous approach if the fork fails?  If the
former - this is what revision history is for, if the latter, I prefer not to
have runtime fallbacks, it is easy to accidentally end up using a fallback which
you didn't think you were using.  

+                    LibraryLoader.nativeForkAndPrefetchNativeLibrary();
                 } catch (ProcessInitException e) {
                     Log.e(TAG, "Unable to load native library.", e);
                     mActivityDelegate.onStartupFailure();