Don't pass URLBlacklistManager from UI to IO through ProfileParams on ProfileIOData.

chrome/browser/profiles/profile_io_data.h

Index: chrome/browser/profiles/profile_io_data.h
diff --git a/chrome/browser/profiles/profile_io_data.h b/chrome/browser/profiles/profile_io_data.h
index 227abb0c05fd813544b18c3912befd2f2d9e2a9b..760a06d249ca034151bf6c634fe4840ea8aa2d29 100644
--- a/chrome/browser/profiles/profile_io_data.h
+++ b/chrome/browser/profiles/profile_io_data.h
@@ -156,9 +156,6 @@ class ProfileIOData {
     // because on linux it relies on initializing things through gconf,
     // and needs to be on the main thread.
     scoped_ptr<net::ProxyConfigService> proxy_config_service;
-    // Initialized on the UI thread because it needs to reference the
-    // Profile's PrefService.
-    scoped_ptr<policy::URLBlacklistManager> url_blacklist_manager;
     // The profile this struct was populated from. It's passed as a void* to
     // ensure it's not accidently used on the IO thread. Before using it on the
     // UI thread, call ProfileManager::IsValidProfile to ensure it's alive.
@@ -168,7 +165,7 @@ class ProfileIOData {
 
   explicit ProfileIOData(bool is_incognito);
 
-  void InitializeProfileParams(Profile* profile);
+  void InitializeOnUIThread(Profile* profile);
   void ApplyProfileParamsToContext(ChromeURLRequestContext* context) const;
 
   // Lazy initializes the ProfileIOData object the first time a request context