[Invalidations] Require there to be no registered handlers on Invalidator destruction

chrome/browser/sync/profile_sync_service_unittest.cc

Index: chrome/browser/sync/profile_sync_service_unittest.cc
diff --git a/chrome/browser/sync/profile_sync_service_unittest.cc b/chrome/browser/sync/profile_sync_service_unittest.cc
index 788d4254cfdb33504dd810ed516cbdf5f91b6f2f..4bd18df6fce0508d130477159002618aab945a15 100644
--- a/chrome/browser/sync/profile_sync_service_unittest.cc
+++ b/chrome/browser/sync/profile_sync_service_unittest.cc
@@ -180,6 +180,7 @@ TEST_F(ProfileSyncServiceTest, InitialState) {
       ProfileSyncService::MANUAL_START,
       true,
       base::Closure()));
+  harness_.service->Initialize();
   EXPECT_TRUE(
       harness_.service->sync_service_url().spec() ==
         ProfileSyncService::kSyncServerUrl ||
@@ -430,6 +431,8 @@ TEST_F(ProfileSyncServiceTest, UpdateRegisteredInvalidationIdsPersistence) {
   backend->EmitOnInvalidatorStateChange(syncer::TRANSIENT_INVALIDATION_ERROR);
   EXPECT_EQ(syncer::TRANSIENT_INVALIDATION_ERROR,
             handler.GetInvalidatorState());
+
+  harness_.service->UnregisterInvalidationHandler(&handler);
 }
 
 // Thin Invalidator wrapper around ProfileSyncService.