Upstream: Renderers are running in WebAPKs.

content/public/android/java/src/org/chromium/content/app/DownloadProcessService.java

Index: content/public/android/java/src/org/chromium/content/app/DownloadProcessService.java
diff --git a/content/public/android/java/src/org/chromium/content/app/DownloadProcessService.java b/content/public/android/java/src/org/chromium/content/app/DownloadProcessService.java
index 7ea954bdd734fab3808ecfd1d4903ea3bab5bb40..b95de2e06ff66aff98b5883b8075f07a7340d11a 100644
--- a/content/public/android/java/src/org/chromium/content/app/DownloadProcessService.java
+++ b/content/public/android/java/src/org/chromium/content/app/DownloadProcessService.java
@@ -40,12 +40,13 @@ public class DownloadProcessService extends ChildProcessService {
     @SuppressLint("NewApi")
     public int onStartCommand(Intent intent, int flags, int startId) {
         assert Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN_MR2;
-        initializeParams(intent);
+        ChildProcessServiceImpl impl = getChildProcessServiceImpl();

[Maria, 2016/06/17 17:09:24]

I think that instead of surfacing the impl and letting code here call it, you
should expose the calls on ChildProcessService and proxy inside the service.
This leaks implementation details.

[Xi Han, 2016/06/17 18:35:20]

That is what I did before. Sorry Peter, revert it back.

+        impl.initializeParams(intent);
         Bundle bundle = intent.getExtras();
         if (bundle != null) {
             IBinder binder = bundle.getBinder(ChildProcessConstants.EXTRA_CHILD_PROCESS_CALLBACK);
             mCallback = IChildProcessCallback.Stub.asInterface(binder);
-            getServiceInfo(bundle);
+            impl.getServiceInfo(bundle);
         }
         return START_STICKY;
     }