Upstream: Renderers are running in WebAPKs.

chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkActivity.java

Index: chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkActivity.java
diff --git a/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkActivity.java b/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkActivity.java
index 7451339ceffe6380806654b5633e306eca19baee..929de692774897865ec4a3a1b9699f0d5686d137 100644
--- a/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkActivity.java
+++ b/chrome/android/java/src/org/chromium/chrome/browser/webapps/WebApkActivity.java
@@ -21,6 +21,7 @@ import org.chromium.content.browser.ChildProcessCreationParams;
 import org.chromium.content_public.browser.LoadUrlParams;
 import org.chromium.ui.base.PageTransition;
 import org.chromium.webapk.lib.client.WebApkServiceConnectionManager;
+import org.chromium.webapk.lib.common.WebApkSandboxedProcessService;
 
 /**
  * An Activity is designed for WebAPKs (native Android apps) and displays a webapp in a nearly
@@ -130,7 +131,8 @@ public class WebApkActivity extends WebappActivity {
         if (isForWebApk) {
             int extraBindFlag = params == null ? 0 : params.getExtraBindFlags();
             params = new ChildProcessCreationParams(getWebappInfo().webApkPackageName(),
-                    extraBindFlag, LibraryProcessType.PROCESS_CHILD);
+                    extraBindFlag, LibraryProcessType.PROCESS_CHILD,
+                    WebApkSandboxedProcessService.class);

[no sievers, 2016/06/23 17:18:50]

Would it also be possible to override through the manifest somehow that this
uses a different service class?

[Xi Han, 2016/06/23 17:34:56]

Do you ask is it possible that we may change the service name in the future? It
might be possible, even though the chance is low.

[no sievers, 2016/06/23 17:45:33]

And also because maybe it's a nicer place than setting it globally here?
Given that you already have to define each service in the manifest anyhow
depending on how many you have (see ChildProcessLauncher.getNumberOfServices()).

I'm also coming a bit from the point of view what really needs to be a
content-public API here (see my comment in other patch).

Generally all the multi-process stuff (or at least all the launching logic) is
more of an implementation detail (at least on other platforms).
Now on Android we have named services that an application already needs to
define in the manifest. But maybe we could just handle all the configuration
there. (Well, I guess for WebView we cannot though.)

[Xi Han, 2016/06/23 18:00:26]

Sounds like maybe we need to introduce something like:
<meta-data android:name="org.chromium.content.browser.CLASS_SANDBOXED_SERVICES"
            android:value="{{ SandboxedProcessServiceClass }}"/>
<meta-data android:name="org.chromium.content.browser.CLASS_PRIVILEGED_SERVICES"
            android:value="{{ PriviledgedProcessServiceClass }}"/>
Only one concern is that we always have to read metadata when the class is
needed.

         }
         ChildProcessCreationParams.set(params);
     }