Split Autofill webdata

chrome/browser/memory_purger.cc

Index: chrome/browser/memory_purger.cc
diff --git a/chrome/browser/memory_purger.cc b/chrome/browser/memory_purger.cc
index 5f3b09f7624aefed60c6cd72fdd13832a7f75408..98ab3011652cfb788548ee695897a33380e4e56a 100644
--- a/chrome/browser/memory_purger.cc
+++ b/chrome/browser/memory_purger.cc
@@ -117,11 +117,11 @@ void MemoryPurger::PurgeBrowser() {
       history_service->UnloadBackend();
 
     // Unload all web databases (freeing memory used to cache sqlite).
-    scoped_refptr<WebDataService> web_data_service =
+    WebDataServiceWrapper* wds_wrapper =
         WebDataServiceFactory::GetForProfileIfExists(
             profiles[i], Profile::EXPLICIT_ACCESS);
-    if (web_data_service.get())
-      web_data_service->UnloadDatabase();
+    if (wds_wrapper && wds_wrapper->GetWebData())
+      wds_wrapper->GetWebData()->UnloadDatabase();

[Jói, 2013/03/20 23:09:10]

Wouldn't this also need to call GetAutofillWebData()->UnloadDatabase()?

[Cait (Slow), 2013/03/21 23:23:27]

hmm...I wonder if we should expose a method on the wrapper to unload the DB
directly? UnloadDatabase is a method on the wds base class, so calling it on
AutofillWD is a no-op after it has been called on wds, but this is not at all
obvious from the current impl.

 
     BrowserContext::PurgeMemory(profiles[i]);
   }