Activate data reduction proxy after profile initialization is complete.

chrome/browser/profiles/profile_manager.cc

Index: chrome/browser/profiles/profile_manager.cc
diff --git a/chrome/browser/profiles/profile_manager.cc b/chrome/browser/profiles/profile_manager.cc
index 21df767c82daec0f7ffc68e9ed40f99aabd73297..39d3ff08e3d76d0b819d9f0f905c315306dea483 100644
--- a/chrome/browser/profiles/profile_manager.cc
+++ b/chrome/browser/profiles/profile_manager.cc
@@ -25,6 +25,8 @@
 #include "chrome/browser/content_settings/host_content_settings_map.h"
 #include "chrome/browser/download/download_service.h"
 #include "chrome/browser/download/download_service_factory.h"
+#include "chrome/browser/net/spdyproxy/data_reduction_proxy_chrome_settings.h"
+#include "chrome/browser/net/spdyproxy/data_reduction_proxy_chrome_settings_factory.h"
 #include "chrome/browser/password_manager/password_store_factory.h"
 #include "chrome/browser/prefs/incognito_mode_prefs.h"
 #include "chrome/browser/profiles/bookmark_model_loaded_observer.h"
@@ -981,6 +983,9 @@ void ProfileManager::DoFinalInit(Profile* profile, bool go_off_the_record) {
   AddProfileToCache(profile);
   DoFinalInitLogging(profile);
 
+  DataReductionProxyChromeSettingsFactory::GetForBrowserContext(profile)->
+      MaybeActivateDataReductionProxy(true);

[sgurun-gerrit only, 2014/10/22 20:25:59]

I am not the owner of this code, but this custom code for DRP here just looks
like a hack to me. is this the only way of achieving this goal?

[Not at Google. Contact bengr, 2014/10/22 20:55:29]

This code was simply moved from being called through ProfileImpl::DoFinalInit()
to here(ProfileManger::DoFinalInit()), so it's about as good or bad as the
previous location. Note that ProfileImpl::DoFinalInit() continues to have custom
DRP code and the call is similar to this one.

I don't know of a better location. We could see if mmenke has suggestions.

[mmenke, 2014/10/23 17:17:26]

Why can't we just do all this on the IO thread?  (Stuff meaning doing the probe,
figuring out what settings to use, etc)?

[Not at Google. Contact bengr, 2014/10/23 17:29:33]

The probe can only be done after profile initialization is complete. More
specifically, only after DoFinalInitForServices(..) on line 982 above. If probe
is done before DoFinalInitForServices(..), then it causes the crash mentioned in
the bug.

SetupDataReductionProxy(..) in io thread is called before the above method
executes, so cannot do it there. Is there any location on io thread which works
for this purpose?

[mmenke, 2014/10/23 17:36:59]

I thought the issue was when you could first make a URLRequest?  You should be
able to them at the end of ProfileIOData::Init.

[Not at Google. Contact bengr, 2014/10/23 17:39:42]

Yes, we connect to the probe with a URLRequest.

[Not at Google. Contact bengr, 2014/10/23 17:40:53]

Trying to connect to the probe with a URLRequest at the end of
ProfileIOData::Init causes the crash mentioned in the bug.

[mmenke, 2014/10/23 17:43:32]

Skimming over the bug, I see no mention of this function, or even ProfileIOData.
 I do see mention of ProfileImpl::DoFinalInit.

+
   ProfileMetrics::LogNumberOfProfiles(this);
   content::NotificationService::current()->Notify(
       chrome::NOTIFICATION_PROFILE_ADDED,