Ensure we don't leak a callback object when starting a sandboxed process.

content/public/android/java/src/org/chromium/content/browser/SandboxedProcessLauncher.java

Index: content/public/android/java/src/org/chromium/content/browser/SandboxedProcessLauncher.java
diff --git a/content/public/android/java/src/org/chromium/content/browser/SandboxedProcessLauncher.java b/content/public/android/java/src/org/chromium/content/browser/SandboxedProcessLauncher.java
index 04a69734f9296365c6bbb1397be9c979b4a00ee7..9cb31b774d4e2fa38545549bce9f2dd9904bfd0f 100644
--- a/content/public/android/java/src/org/chromium/content/browser/SandboxedProcessLauncher.java
+++ b/content/public/android/java/src/org/chromium/content/browser/SandboxedProcessLauncher.java
@@ -180,6 +180,8 @@ public class SandboxedProcessLauncher {
         if (allocatedConnection == null) {
             allocatedConnection = allocateBoundConnection(context, commandLine);
             if (allocatedConnection == null) {
+                // Notify the native code so it can free the heap allocated callback.
+                nativeOnSandboxedProcessStarted(clientContext, 0);
                 return;
             }
         }