Clean up BrowsingDataAppCacheHelper

chrome/browser/browsing_data/browsing_data_appcache_helper.cc

Index: chrome/browser/browsing_data/browsing_data_appcache_helper.cc
diff --git a/chrome/browser/browsing_data/browsing_data_appcache_helper.cc b/chrome/browser/browsing_data/browsing_data_appcache_helper.cc
index ddb9c709b0cb1b66b2279f49d73e264d210a5e70..acbd5edff25a53f94fd3f141648d5c1613ed9d5d 100644
--- a/chrome/browser/browsing_data/browsing_data_appcache_helper.cc
+++ b/chrome/browser/browsing_data/browsing_data_appcache_helper.cc
@@ -7,19 +7,18 @@
 #include "base/bind.h"
 #include "base/bind_helpers.h"
 #include "chrome/browser/browsing_data/browsing_data_helper.h"
-#include "chrome/browser/profiles/profile.h"
-#include "chrome/common/url_constants.h"
 #include "content/public/browser/browser_context.h"
 #include "content/public/browser/browser_thread.h"
 #include "content/public/browser/storage_partition.h"
 
-using content::BrowserThread;
 using content::BrowserContext;
+using content::BrowserThread;
 
-BrowsingDataAppCacheHelper::BrowsingDataAppCacheHelper(Profile* profile)
+BrowsingDataAppCacheHelper::BrowsingDataAppCacheHelper(
+    BrowserContext* browser_context)
     : is_fetching_(false),
-      appcache_service_(BrowserContext::GetDefaultStoragePartition(profile)->
-                            GetAppCacheService()) {
+      appcache_service_(BrowserContext::GetDefaultStoragePartition(
+                            browser_context)->GetAppCacheService()) {
 }
 
 void BrowsingDataAppCacheHelper::StartFetching(const base::Closure& callback) {
@@ -36,11 +35,10 @@ void BrowsingDataAppCacheHelper::StartFetching(const base::Closure& callback) {
   }
 
   DCHECK_CURRENTLY_ON(BrowserThread::IO);
-  appcache_info_callback_.Reset(
+  appcache_service_->GetAllAppCacheInfo(

[Bernhard Bauer, 2014/09/05 16:15:12]

So, what happens when this object is destroyed now?

[vabr (Chromium), 2014/09/19 12:35:47]

Thanks for catching this. I was confused when first reading the
CancellableCallback definition -- it does not Cancel() itself on destruction,
and neither is Cancel() called by BrowsingDataAppCacheHelper on destruction. But
I missed that the CancellableCallback binds the wrapped callback to a weak
pointer to itself, so this effectively cancels the callback on the destruction
of CancellableCallback (and it's owner).

Therefore, putting appcache_info_callback_ back.

+      info_collection_.get(),
       base::Bind(&BrowsingDataAppCacheHelper::OnFetchComplete,
                  base::Unretained(this)));
-  appcache_service_->GetAllAppCacheInfo(info_collection_.get(),
-                                        appcache_info_callback_.callback());
 }
 
 void BrowsingDataAppCacheHelper::DeleteAppCacheGroup(
@@ -87,16 +85,16 @@ void BrowsingDataAppCacheHelper::OnFetchComplete(int rv) {
 }
 
 CannedBrowsingDataAppCacheHelper::CannedBrowsingDataAppCacheHelper(
-    Profile* profile)
-    : BrowsingDataAppCacheHelper(profile),
-      profile_(profile) {
+    BrowserContext* browser_context)
+    : BrowsingDataAppCacheHelper(browser_context),
+      browser_context_(browser_context) {
   info_collection_ = new content::AppCacheInfoCollection;
 }
 
 CannedBrowsingDataAppCacheHelper* CannedBrowsingDataAppCacheHelper::Clone() {
   DCHECK_CURRENTLY_ON(BrowserThread::UI);
   CannedBrowsingDataAppCacheHelper* clone =
-      new CannedBrowsingDataAppCacheHelper(profile_);
+      new CannedBrowsingDataAppCacheHelper(browser_context_);
 
   clone->info_collection_->infos_by_origin = info_collection_->infos_by_origin;
   return clone;