Remove more unnecessary ChromeURLRequestContext members.

chrome/browser/browser_main.cc

Index: chrome/browser/browser_main.cc
diff --git a/chrome/browser/browser_main.cc b/chrome/browser/browser_main.cc
index 4615c720792ccf3d1f23975f9f4b87d8d136ffb9..e580e035403d792081c2205ec2777e31d1c3c2e1 100644
--- a/chrome/browser/browser_main.cc
+++ b/chrome/browser/browser_main.cc
@@ -2008,8 +2008,14 @@ int BrowserMain(const MainFunctionParams& parameters) {
 
       // If we're running tests (ui_task is non-null), then we don't want to
       // call FetchLanguageListFromTranslateServer
-      if (parameters.ui_task == NULL && translate_manager != NULL)
+      if (parameters.ui_task == NULL && translate_manager != NULL) {
+        // TODO(willchan): Get rid of this after TranslateManager doesn't use
+        // the default request context. http://crbug.com/89396.
+        // This is necessary to force |default_request_context_| to be
+        // initialized.
+        profile->GetRequestContext();

[Dmitry Polukhin, 2011/07/18 08:47:23]

It looks like removing this line broke Chrome on Chrome OS on login screen.
[12795:12795:1542236166900:FATAL:url_fetcher.cc(558)] Check failed:
request_context_getter_. We need an URLRequestContext!
Backtrace:
	base::debug::StackTrace::StackTrace() [0xf3593398]
	logging::LogMessage::~LogMessage() [0xf35b28b1]
	URLFetcher::Core::Start() [0xf412b4d9]
	URLFetcher::Start() [0xf412e3c2]
	TranslateManager::FetchLanguageListFromTranslateServer() [0xf2c1df8f]
	BrowserMain() [0xf2782c0e]
	(anonymous namespace)::RunNamedProcessTypeMain() [0xf26db5f0]
	ChromeMain [0xf26dc012]
	main [0xf26dcbc9]

[Dmitry Polukhin, 2011/07/18 09:06:12]

This line is not guilty. But CL that broke Chrome is right. I reverted it
locally and Chrome is able to show login screen.  

[willchan no longer on Chromium, 2011/07/18 10:20:32]

I had encountered that stacktrace earlier in the ChromeOS tests and fixed it by
adding this line. Are you sure you are running a build that includes r92804? I'm
surprised that I could encounter this stacktrace on the bots, fix it, but that
you would still see it. Maybe there's different behavior in the build that's not
covered in tests?

         translate_manager->FetchLanguageListFromTranslateServer(user_prefs);
+      }
 
       RunUIMessageLoop(browser_process.get());
     }