Properly handle screen recorder shutdown in ChromotingHost.

remoting/host/chromoting_host.h

Index: remoting/host/chromoting_host.h
diff --git a/remoting/host/chromoting_host.h b/remoting/host/chromoting_host.h
index fb26aec8d349a36232596348a62d61012abe0ea1..9f9b10e5fed6fc2906398ad9f951e0a0b7b23f42 100644
--- a/remoting/host/chromoting_host.h
+++ b/remoting/host/chromoting_host.h
@@ -182,6 +182,9 @@ class ChromotingHost : public base::RefCountedThreadSafe<ChromotingHost>,
   void ProcessPreAuthentication(
       const scoped_refptr<protocol::ConnectionToClient>& connection);
 
+  void StopScreenRecorder();
+  void OnScreenRecorderStopped();
+
   // The following methods are called during shutdown.
   void ShutdownNetwork();
   void ShutdownRecorder();
@@ -212,6 +215,9 @@ class ChromotingHost : public base::RefCountedThreadSafe<ChromotingHost>,
   // and read by jingle thread.
   State state_;
 
+  // Number of screen recorders that are currently being stopped.

[dmac, 2011/08/11 23:56:34]

Maybe expand this comment to explain the case that you explained to me? eg we
are we worried about this?

[Sergey Ulanov, 2011/08/12 00:29:48]

Done.

+  int stopping_recorders_;
+
   // Lock is to lock the access to |state_|.
   base::Lock lock_;