Assert that thread-safe reference counting is used with...

chrome_frame/chrome_frame_automation.cc

Index: chrome_frame/chrome_frame_automation.cc
===================================================================
--- chrome_frame/chrome_frame_automation.cc	(revision 27168)
+++ chrome_frame/chrome_frame_automation.cc	(working copy)
@@ -144,8 +144,8 @@
 }
 
 template <> struct RunnableMethodTraits<ProxyFactory> {
-  static void RetainCallee(ProxyFactory* obj) {}
-  static void ReleaseCallee(ProxyFactory* obj) {}
+  void RetainCallee(ProxyFactory* obj) {}
+  void ReleaseCallee(ProxyFactory* obj) {}
 };
 
 ProxyFactory::ProxyFactory()
@@ -600,7 +600,7 @@
       "ChromeFrame.HostNetworking", !use_chrome_network_, 0, 1, 2);
 
   UMA_HISTOGRAM_CUSTOM_COUNTS(
-      "ChromeFrame.HandleTopLevelRequests", handle_top_level_requests_, 0, 1, 
+      "ChromeFrame.HandleTopLevelRequests", handle_top_level_requests_, 0, 1,
       2);
 
   IPC::SyncMessage* message =
@@ -779,7 +779,7 @@
 void ChromeFrameAutomationClient::ReleaseAutomationServer() {
   DLOG(INFO) << __FUNCTION__;
   if (automation_server_id_) {
-    // Cache the server id and clear the automation_server_id_ before 
+    // Cache the server id and clear the automation_server_id_ before
     // calling ReleaseAutomationServer.  The reason we do this is that
     // we must cancel pending messages before we release the automation server.
     // Furthermore, while ReleaseAutomationServer is running, we could get
Property changes on: chrome_frame\chrome_frame_automation.cc
___________________________________________________________________
Added: svn:eol-style
   + LF