Call SetApplicationIsDaemon() in V2 sandbox.

content/common/sandbox_init_mac.h

Index: content/common/sandbox_init_mac.h
diff --git a/content/common/sandbox_init_mac.h b/content/common/sandbox_init_mac.h
index 8f860efd048daa9196d88e82c5e573ee6ab62b24..ea41dbe31c14f3b8b221bffcf7f76a3de672d148 100644
--- a/content/common/sandbox_init_mac.h
+++ b/content/common/sandbox_init_mac.h
@@ -15,6 +15,13 @@ namespace content {
 // returned.
 bool InitializeSandbox();
 
+// These two functions expose the warmup and initialization on the sandbox as
+// separate operations. This allows callers to perform specific operations after
+// the sandbox is warmed up but before it is enabled.
+void ExplicitlyWarmupSandbox();

[Robert Sesek, 2017/07/06 21:28:09]

I know this is probably temporary code, but this interface seems rather
error-prone. I thought of something else, though: add a new InitializeSandbox()
function that takes a base::Closure to run after warmup has completed but before
the sandbox is initialized. Something like this:

bool InitializeSandboxWithPostWarmupHook(base::OnceClosure hook);

… and then InitializeSandbox() could be implemented in terms of that with a null
callback. 

[Greg K, 2017/07/07 18:10:21]

Done.

+
+bool ExplicitlyEnableSandbox();
+
 }  // namespace content
 
 #endif  // CONTENT_COMMON_SANDBOX_INIT_MAC_H_