Fix destruction order between SurfaceManger and OffscreenCanvasSurfaceImpl

cc/surfaces/surface_factory.h

Index: cc/surfaces/surface_factory.h
diff --git a/cc/surfaces/surface_factory.h b/cc/surfaces/surface_factory.h
index c869029cbaabe66cefb25c4934a5368bc9c7980c..99f0aeb54d1d4344775161248604dd4f1d684ea2 100644
--- a/cc/surfaces/surface_factory.h
+++ b/cc/surfaces/surface_factory.h
@@ -83,6 +83,10 @@ class CC_SURFACES_EXPORT SurfaceFactory
   bool needs_sync_points() const { return needs_sync_points_; }
   void set_needs_sync_points(bool needs) { needs_sync_points_ = needs; }
 
+  // SurfaceFactory's owner can call this when it finds out that SurfaceManager
+  // is no longer alive during destruction.
+  void didDestroySurfaceManager() { manager_ = nullptr; }

[jbauman, 2016/06/23 19:46:57]

This should be called DidDestroySurfaceManager in chromium style.

[xlai (Olivia), 2016/06/23 20:09:28]

Sorry I just landed the patch after being pushed to fix beta-blocker asap. I'll
follow up with a patch (if this one is not reverted) to fix style here and some
other places. 
Actually, I'm thinking probably "did_destroy_surface_manager()" may be better
because according to Google C++ guide it says cheap function like this may use
this style.

+
  private:
   SurfaceManager* manager_;
   SurfaceFactoryClient* client_;