Kill CleanUpAfterMessageLoopDestruction.

chrome/browser/browser_process_sub_thread.cc

 // Copyright (c) 2010 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/browser_process_sub_thread.h"
 #include "build/build_config.h"
 #include "chrome/common/notification_service.h"
 
 #if defined(OS_WIN)
 #include <Objbase.h>
@@ skipping 10 matching lines @@
 
 void BrowserProcessSubThread::Init() {
 #if defined(OS_WIN)
   // Initializes the COM library on the current thread.
   CoInitialize(NULL);
 #endif
 
   notification_service_ = new NotificationService;
 }
 
-void BrowserProcessSubThread::CleanUpAfterMessageLoopDestruction() {
+void BrowserProcessSubThread::CleanUp() {
   delete notification_service_;

[eroman, 2011/03/02 02:23:31]

hopefully there aren't any destruction observers that indirectly access the
notification service, otherwise they will now be accessing deleted memory... man
i hate the destruction observers :)

   notification_service_ = NULL;
 
 #if defined(OS_WIN)
   // Closes the COM library on the current thread. CoInitialize must
   // be balanced by a corresponding call to CoUninitialize.
   CoUninitialize();
 #endif
 }