Bring skydebugger closer to clean-shutdown

mojo/services/surfaces/surfaces_impl.cc

Index: mojo/services/surfaces/surfaces_impl.cc
diff --git a/mojo/services/surfaces/surfaces_impl.cc b/mojo/services/surfaces/surfaces_impl.cc
index 95ff5c16800864c7aef3df74467bd3842e925268..13956a5dd8863b762de35a9de445433afdcce416 100644
--- a/mojo/services/surfaces/surfaces_impl.cc
+++ b/mojo/services/surfaces/surfaces_impl.cc
@@ -25,6 +25,9 @@ SurfacesImpl::SurfacesImpl(cc::SurfaceManager* manager,
 }
 
 SurfacesImpl::~SurfacesImpl() {
+  // Destory any outstanding surfaces when the connection goes down for any

[jamesr, 2014/11/05 19:02:24]

s/Destory/Destroy/

+  // reason to avoid ~SurfaceFactory() logging about us failing to do so.

[jamesr, 2014/11/05 19:02:24]

this comment is misleading. we aren't destroying to avoid a log message, we're
destroying because when the connection is gone all surfaces we might want to
manage should be destroyed.

we might need to refine this in the future

+  factory_.DestroyAll();
 }
 
 void SurfacesImpl::CreateSurface(SurfaceIdPtr id, mojo::SizePtr size) {