Have the unload event execute in background on cross-site navigations

chrome/browser/renderer_host/web_cache_manager_browsertest.cc

Index: chrome/browser/renderer_host/web_cache_manager_browsertest.cc
diff --git a/chrome/browser/renderer_host/web_cache_manager_browsertest.cc b/chrome/browser/renderer_host/web_cache_manager_browsertest.cc
index a917ed5cba1dbbc8b3a6d9b1e8b265ca62be306c..4c884ae7c4ad3fed2ea4b571e9eb0abacac6d31a 100644
--- a/chrome/browser/renderer_host/web_cache_manager_browsertest.cc
+++ b/chrome/browser/renderer_host/web_cache_manager_browsertest.cc
@@ -57,10 +57,16 @@ IN_PROC_BROWSER_TEST_F(WebCacheManagerBrowserTest, CrashOnceOnly) {
 
   ui_test_utils::NavigateToURL(browser(), url);
 
-  EXPECT_EQ(
-      WebCacheManager::GetInstance()->active_renderers_.size(), 1U);
+  // We may have two renderers if one is still executing the unload event in the

[Charlie Reis, 2013/12/09 20:12:29]

Slight concern: Are we likely to have many flaky tests if we don't know when a
renderer is going to go away?

+  // background.
+  EXPECT_GT(
+      WebCacheManager::GetInstance()->active_renderers_.size(), 0U);
+  EXPECT_LT(
+      WebCacheManager::GetInstance()->active_renderers_.size(), 3U);
   EXPECT_EQ(
       WebCacheManager::GetInstance()->inactive_renderers_.size(), 0U);
-  EXPECT_EQ(
-      WebCacheManager::GetInstance()->stats_.size(), 1U);
+  EXPECT_GT(
+      WebCacheManager::GetInstance()->stats_.size(), 0U);
+  EXPECT_LT(
+      WebCacheManager::GetInstance()->stats_.size(), 3U);
 }