Detach the output surface if bind fails.

cc/output/output_surface.cc

Index: cc/output/output_surface.cc
diff --git a/cc/output/output_surface.cc b/cc/output/output_surface.cc
index 30864f1ff548e45b767f22b9ace117173015a7a9..08bb4d21b150244df9cca60bc2b8012f269880f4 100644
--- a/cc/output/output_surface.cc
+++ b/cc/output/output_surface.cc
@@ -214,7 +214,7 @@ bool OutputSurface::BindToClient(OutputSurfaceClient* client) {
   }
 
   if (!success)
-    client_ = NULL;
+    DetachFromClient();

[piman, 2016/05/06 19:41:40]

this will do the MemoryDumpManager::GetInstance()->UnregisterDumpProvider thing
- before the Register below.

Should we either:
1- do this after the register (i.e. in case of failure we register and
unregister immediately)
2- only register & unregister in case of success?

[danakj, 2016/05/06 20:19:56]

Argh OutputSurface. There are a lot of bad options here.

We can rely on the sub classes calling the base class BindToClient first and
early outting if it failed. Then we don't need to call the virtual
DetachFromClient and we could just clean up ourselves.

Or we can avoid that dependency, but then we need to register just to
unregister, as you say. Or store some extra state on this class to know that we
didn't fully finish BindToClient.

 
   // In certain cases, ThreadTaskRunnerHandle isn't set (Android Webview).
   // Don't register a dump provider in these cases.