Make WebRtcLoggingHandlerHost tolerant of out-of-order messages.

chrome/browser/media/webrtc_logging_handler_host.cc

Index: chrome/browser/media/webrtc_logging_handler_host.cc
diff --git a/chrome/browser/media/webrtc_logging_handler_host.cc b/chrome/browser/media/webrtc_logging_handler_host.cc
index bed00cb8757700aefc32b44e7e6485991aaf0205..3467e8b11667727038ffc35e39a76a73bc526ea6 100644
--- a/chrome/browser/media/webrtc_logging_handler_host.cc
+++ b/chrome/browser/media/webrtc_logging_handler_host.cc
@@ -219,6 +219,12 @@ bool WebRtcLoggingHandlerHost::OnMessageReceived(const IPC::Message& message,
 
 void WebRtcLoggingHandlerHost::OnLoggingStoppedInRenderer() {
   DCHECK(BrowserThread::CurrentlyOn(BrowserThread::IO));
+  if (logging_state_ != STOPPING) {
+    // If an out-of-order response is received, stop_callback_ may be invalid,
+    // and must not be invoked.
+    BadMessageReceived();

[tommi (sloooow) - chröme, 2014/01/14 15:14:22]

perhaps log an error and the current value of logging_state_?

+    return;
+  }
   logging_state_ = STOPPED;
   FireGenericDoneCallback(&stop_callback_, true, "");
 }