Fix test-running in --single-process mode.

chrome/browser/profiles/profile_destroyer.cc

Index: chrome/browser/profiles/profile_destroyer.cc
diff --git a/chrome/browser/profiles/profile_destroyer.cc b/chrome/browser/profiles/profile_destroyer.cc
index 59f7dd5ad7c954d9ded6f902305e5c1e4afac458..0ab0aa008866f2d29238d3f15d0a5495d760dbf3 100644
--- a/chrome/browser/profiles/profile_destroyer.cc
+++ b/chrome/browser/profiles/profile_destroyer.cc
@@ -37,7 +37,8 @@ void ProfileDestroyer::DestroyProfileWhenAppropriate(Profile* const profile) {
   }
   // This should never happen for non Off the record profile, this means that
   // there is a leak in a render process host that MUST BE FIXED!!!
-  DCHECK(hosts.empty() || profile->IsOffTheRecord());
+  DCHECK(content::RenderProcessHost::run_renderer_in_process() ||

[MAD, 2012/12/15 00:11:22]

Can you please add a comment stating why we need to do this?

[Jeffrey Yasskin, 2012/12/15 00:31:31]

Sure. Could you explain why off-the-record profiles leave RenderProcessHosts
around so the resulting comment is symmetric?

[MAD, 2012/12/15 04:05:31]

Good point, this is because we don't want to delay destruction of off the record
profile, since they contain private information that has be destroyed as quickly
as possible.

+         hosts.empty() || profile->IsOffTheRecord());
   // Note that we still test for !profile->IsOffTheRecord here even though we
   // DCHECK'd above because we want to protect Release builds against this even
   // we need to identify if there are leaks when we run Debug builds.