Merge "Start the webview_zygote at boot, but in the background." into pi-dev

am: ea50ff85e8

Change-Id: Ibb64aa53c366d473a131998af409784add519be7
This commit is contained in:
Torne (Richard Coles)
2018-03-14 21:06:21 +00:00
committed by android-build-merger

View File

@@ -19,6 +19,7 @@ package android.webkit;
import android.app.LoadedApk;
import android.content.pm.ApplicationInfo;
import android.content.pm.PackageInfo;
import android.os.AsyncTask;
import android.os.Build;
import android.os.ChildZygoteProcess;
import android.os.Process;
@@ -93,11 +94,17 @@ public class WebViewZygote {
synchronized (sLock) {
sMultiprocessEnabled = enabled;
// When multi-process is disabled, kill the zygote. When it is enabled,
// the zygote is not explicitly started here to avoid waiting on the
// zygote launch at boot. Instead, the zygote will be started when it is
// first needed in getProcess().
if (!enabled) {
// When toggling between multi-process being on/off, start or stop the
// zygote. If it is enabled and the zygote is not yet started, launch it.
// Otherwise, kill it. The name may be null if the package information has
// not yet been resolved.
if (enabled) {
// Run on a background thread as this waits for the zygote to start and we don't
// want to block the caller on this. It's okay if this is delayed as anyone trying
// to use the zygote will call it first anyway.
AsyncTask.THREAD_POOL_EXECUTOR.execute(WebViewZygote::getProcess);
} else {
// No need to run this in the background, it's very brief.
stopZygoteLocked();
}
}