Initialize the chrome thread object at the start of the CFUrlRequestUnittestRunner constructor.

This causes a CHECK to fire in the extensions service initialization which happens when we 
initialize the profile. The CHECK was added in revision 30550. Given the spate of these test
failures we should really speed up the process of moving the chrome frame builder to the main
waterfall.

TBR=tommi


Review URL: http://codereview.chromium.org/346019

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30556 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 4 insertions, 4 deletions

diff --git a/chrome_frame/test/net/fake_external_tab.cc b/chrome_frame/test/net/fake_external_tab.cc
index 53ac162..63ddf87 100644
--- a/chrome_frame/test/net/fake_external_tab.cc
+++ b/chrome_frame/test/net/fake_external_tab.cc
@@ -142,14 +142,14 @@ void FakeExternalTab::Shutdown() {
 CFUrlRequestUnittestRunner::CFUrlRequestUnittestRunner(int argc, char** argv)
     : NetTestSuite(argc, argv),
       chrome_frame_html_("/chrome_frame", kChromeFrameHtml) {
-  fake_chrome_.Initialize();
-  pss_subclass_.reset(new ProcessSingletonSubclass(this));
-  EXPECT_TRUE(pss_subclass_->Subclass(fake_chrome_.user_data()));
-  StartChromeFrameInHostBrowser();
   // Register the main thread by instantiating it, but don't call any methods.
   main_thread_.reset(new ChromeThread(ChromeThread::UI,
                                       MessageLoop::current()));
   DCHECK(ChromeThread::CurrentlyOn(ChromeThread::UI));
+  fake_chrome_.Initialize();
+  pss_subclass_.reset(new ProcessSingletonSubclass(this));
+  EXPECT_TRUE(pss_subclass_->Subclass(fake_chrome_.user_data()));
+  StartChromeFrameInHostBrowser();
 }
 
 CFUrlRequestUnittestRunner::~CFUrlRequestUnittestRunner() {