Zygote most of the uses of the utility process on Linux

chrome/browser/extensions/extension_management_api.cc

Index: chrome/browser/extensions/extension_management_api.cc
diff --git a/chrome/browser/extensions/extension_management_api.cc b/chrome/browser/extensions/extension_management_api.cc
index 361a4ae28a2d32183666544f3dfa7eac8a466117..1b746b1d28c2f7537f75950683c2708ba14ece1b 100644
--- a/chrome/browser/extensions/extension_management_api.cc
+++ b/chrome/browser/extensions/extension_management_api.cc
@@ -212,6 +212,9 @@ class SafeManifestJSONParser : public UtilityProcessHost::Client {
   void StartWorkOnIOThread() {
     CHECK(BrowserThread::CurrentlyOn(BrowserThread::IO));
     utility_host_ = new UtilityProcessHost(this, BrowserThread::IO);
+#if defined(OS_LINUX)
+    utility_host_->set_should_use_zygote(true);

[Aaron Boodman, 2011/12/02 03:10:04]

Since most call sites want the zygote enabled, how about defaulting to true.

[Jorge Lucangeli Obes, 2011/12/02 18:27:16]

The good thing about defaulting to false is that we can't accidentally break
users of the utility process that are requiring FS access. I went through my
local checkout carefully and used code search to find all users of
UtilityProcessHost, but I felt it would be safer to keep the default as false.

[Jorge Lucangeli Obes, 2011/12/02 20:43:48]

Actually, scratch that. I'm pretty sure I got all the uses. Let's make the
default true.

+#endif
     utility_host_->Send(new ChromeUtilityMsg_ParseJSON(manifest_));
   }