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

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

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 package org.chromium.content.browser;
 
 import android.content.Context;
 import android.os.RemoteException;
 import android.util.Log;
 import android.view.Surface;
@@ skipping 162 matching lines @@
             final int clientContext) {
         assert clientContext != 0;
         SandboxedProcessConnection allocatedConnection;
         synchronized (SandboxedProcessLauncher.class) {
             allocatedConnection = mSpareConnection;
             mSpareConnection = null;
         }
         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;
             }
         }
         final SandboxedProcessConnection connection = allocatedConnection;
         Log.d(TAG, "Setting up connection to process: slot=" + connection.getServiceNumber());
         // Note: This runnable will be executed when the sandboxed connection is setup.
         final Runnable onConnect = new Runnable() {
             @Override
             public void run() {
                 final int pid = connection.getPid();
@@ skipping 97 matching lines @@
                 // avoid waiting for the finalizer to get around to it.
                 if (surface != null) {
                     surface.release();
                 }
             }
         };
     };
 
     private static native void nativeOnSandboxedProcessStarted(int clientContext, int pid);
 }