Remove app context init from LibraryLoader.

base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java

Index: base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java
diff --git a/base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java b/base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java
index 454b167c9e20559b6fbefbec71f96945a7945c90..03495eeb3910e41cc7b81c16f2df1195c3fe01a3 100644
--- a/base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java
+++ b/base/android/java/src/org/chromium/base/library_loader/LibraryLoader.java
@@ -133,8 +133,6 @@ public class LibraryLoader {
      *  @param context The context in which the method is called.
      */
     public void ensureInitialized(Context context) throws ProcessInitException {

[Torne, 2016/08/18 14:44:55]

Why do we still need to pass the app context in here as a parameter if we're
requiring that all callers already set the global app context? Couldn't we just
use ContextUtils inside here to get it, preventing any possibility that it's
different?

[Peter Wen, 2016/08/18 16:30:01]

Done.

We can actually do this at all the places where application context is needed,
but I'll avoid bloating this CL even more. :)

-        // TODO(wnwen): Move this call appropriately down to the tests that need it.
-        ContextUtils.initApplicationContext(context.getApplicationContext());
         synchronized (sLock) {
             if (mInitialized) {
                 // Already initialized, nothing to do.