Call crypto::InitializeTPMToken on the IO thread

chrome/browser/chromeos/login/login_utils_browsertest.cc

Index: chrome/browser/chromeos/login/login_utils_browsertest.cc
diff --git a/chrome/browser/chromeos/login/login_utils_browsertest.cc b/chrome/browser/chromeos/login/login_utils_browsertest.cc
index db1638722b8abdd2ddfaaf286619a0b58e886d86..00eebcd800d046e211f78b49d743265a0792b1b8 100644
--- a/chrome/browser/chromeos/login/login_utils_browsertest.cc
+++ b/chrome/browser/chromeos/login/login_utils_browsertest.cc
@@ -281,7 +281,7 @@ class LoginUtilsTest : public testing::Test,
 
     // IOThread creates ProxyConfigServiceImpl which in turn needs
     // NetworkHandler. Thus initialize it here before creating IOThread.
-    NetworkHandler::Initialize();
+    NetworkHandler::InitializeForTest();

[pneubeck (no reviews), 2013/06/07 14:00:49]

This test has an IOThread, will it be harmful that CertLoader now doesn't use it
but runs crypto on another thread?

[stevenjb, 2013/06/07 20:48:14]

Running crypto tasks on the UI thread should be safe, just slower, which should
be OK for tests.

 
     io_thread_state_.reset(new IOThread(local_state_.Get(),
                                         browser_process_->policy_service(),