Add the ability to unload the HistoryBackend.

A small number of places used accessors like in_memory_url_database() or backend_loaded() with the expectation that if they weren't already functional, the history system was in the process of making them so.  I elected to make both of these functions that triggered lazy backend initialization.

BUG=23400
TEST=none
Review URL: http://codereview.chromium.org/267019

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@28461 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 0 deletions

diff --git a/chrome/browser/profile.cc b/chrome/browser/profile.cc
index 2099e99..4508644 100644
--- a/chrome/browser/profile.cc
+++ b/chrome/browser/profile.cc
@@ -312,6 +312,10 @@ class OffTheRecordProfileImpl : public Profile,
     }
   }
 
+  virtual HistoryService* GetHistoryServiceWithoutCreating() {
+    return profile_->GetHistoryServiceWithoutCreating();
+  }
+
   virtual FaviconService* GetFaviconService(ServiceAccessType sat) {
     if (sat == EXPLICIT_ACCESS) {
       return profile_->GetFaviconService(sat);
@@ -1027,6 +1031,10 @@ HistoryService* ProfileImpl::GetHistoryService(ServiceAccessType sat) {
   return history_service_.get();
 }
 
+HistoryService* ProfileImpl::GetHistoryServiceWithoutCreating() {
+  return history_service_.get();
+}
+
 TemplateURLModel* ProfileImpl::GetTemplateURLModel() {
   if (!template_url_model_.get())
     template_url_model_.reset(new TemplateURLModel(this));