Start the WebKit thread when we initialize the resource dispatcher host

chrome/browser/renderer_host/resource_dispatcher_host_unittest.cc

Index: chrome/browser/renderer_host/resource_dispatcher_host_unittest.cc
===================================================================
--- chrome/browser/renderer_host/resource_dispatcher_host_unittest.cc	(revision 32803)
+++ chrome/browser/renderer_host/resource_dispatcher_host_unittest.cc	(working copy)
@@ -320,8 +320,7 @@
 }
 
 // Tests whether many messages get dispatched properly.
-// TODO(jorlow): Re-enable once bug 28364 is fixed.
-TEST_F(ResourceDispatcherHostTest, DISABLED_TestMany) {
+TEST_F(ResourceDispatcherHostTest, TestMany) {
   EXPECT_EQ(0, host_.GetOutstandingRequestsMemoryCost(0));
 
   MakeTestRequest(0, 1, URLRequestTestJob::test_url_1());
@@ -347,8 +346,7 @@
 
 // Tests whether messages get canceled properly. We issue three requests,
 // cancel one of them, and make sure that each sent the proper notifications.
-// TODO(jorlow): Re-enable once bug 28364 is fixed.
-TEST_F(ResourceDispatcherHostTest, DISABLED_Cancel) {
+TEST_F(ResourceDispatcherHostTest, Cancel) {
   EXPECT_EQ(0, host_.GetOutstandingRequestsMemoryCost(0));
 
   MakeTestRequest(0, 1, URLRequestTestJob::test_url_1());
@@ -608,8 +606,7 @@
 // away.  Note that we rely on Purify for finding the leaks if any.
 // If this test turns the Purify bot red, check the ResourceDispatcherHost
 // destructor to make sure the blocked requests are deleted.
-// TODO(jorlow): Re-enable once bug 28364 is fixed.
-TEST_F(ResourceDispatcherHostTest, DISABLED_TestBlockedRequestsDontLeak) {
+TEST_F(ResourceDispatcherHostTest, TestBlockedRequestsDontLeak) {
   // This second receiver is used to emulate a second process.
   ForwardingReceiver second_receiver(this);