Fix ChromeFrame test failures on IE8 which occurred because we did not handle the case

chrome/browser/automation/automation_resource_message_filter.cc

Index: chrome/browser/automation/automation_resource_message_filter.cc
===================================================================
--- chrome/browser/automation/automation_resource_message_filter.cc	(revision 107804)
+++ chrome/browser/automation/automation_resource_message_filter.cc	(working copy)
@@ -262,7 +262,11 @@
 
   RenderViewMap::iterator automation_details_iter(
       filtered_render_views_.Get().find(renderer_key));
-  if (automation_details_iter != filtered_render_views_.Get().end()) {
+  // We need to match the renderer key and the AutomationResourceMessageFilter
+  // instances. If the filter instances are different it means that a new
+  // automation channel (External host process) was created for this tab.
+  if (automation_details_iter != filtered_render_views_.Get().end() &&
+      automation_details_iter->second.filter == filter) {
     DCHECK_GT(automation_details_iter->second.ref_count, 0);
     automation_details_iter->second.ref_count++;
     // The tab handle may have changed:-