Correct the order of destruction of ProfileImplIOData and ExtensionProcessManager. This was causi...

chrome/browser/profiles/profile_io_data.cc

Index: chrome/browser/profiles/profile_io_data.cc
===================================================================
--- chrome/browser/profiles/profile_io_data.cc	(revision 110070)
+++ chrome/browser/profiles/profile_io_data.cc	(working copy)
@@ -49,6 +49,7 @@
 #include "content/browser/renderer_host/media/media_stream_manager.h"
 #include "content/browser/renderer_host/resource_dispatcher_host.h"
 #include "content/browser/renderer_host/resource_dispatcher_host_request_info.h"
+#include "content/browser/renderer_host/render_process_host.h"
 #include "content/browser/resource_context.h"
 #include "content/public/browser/browser_thread.h"
 #include "content/public/browser/notification_service.h"
@@ -541,6 +542,7 @@
 
 void ProfileIOData::ShutdownOnUIThread() {
   DCHECK(BrowserThread::CurrentlyOn(BrowserThread::UI));
+  DCHECK_EQ(0, RenderProcessHost::AllHostsCount());

[willchan no longer on Chromium, 2011/11/17 20:11:32]

I'd love to upgrade this to a CHECK so we can catch regressions, since if this
is wrong, we're likely to crash later. That said, it's not clear to me that this
fix will fix ALL bugs, so it's probably best to leave it as a DCHECK_EQ right
now, but add a comment to upgrade it to a CHECK later, and do it maybe a week or
two later after we get dev channel results.

[robertshield, 2011/11/17 21:00:43]

Good idea, comment added.

   enable_referrers_.Destroy();
   clear_local_state_on_exit_.Destroy();
   safe_browsing_enabled_.Destroy();