From 55474b575e7e36bea6e7ce2ed18b34ff98a654dc Mon Sep 17 00:00:00 2001 From: "tim@chromium.org" Date: Tue, 14 Apr 2009 22:05:33 +0000 Subject: Give each HistoryService instance it's own backend thread. I had originally planned to push history_thread up to BrowserProcess, but was scared away by the comment in ~Profile that talks about HistoryService calling back into the bookmark bar model, and that it depended on join()ing at that particular time to ensure this doesn't happen after the bookmark bar model has been reset. I didn't use scoped_ptr for the thread because it makes the little dance in CleanUp awkward. TEST=any existing test that exersizes the history service. I added a ProfileManager test that would fail without this change. Review URL: http://codereview.chromium.org/73012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13703 0039d316-1c4b-4281-b951-d872f2087c98 --- chrome/browser/chrome_thread.cc | 2 -- 1 file changed, 2 deletions(-) (limited to 'chrome/browser/chrome_thread.cc') diff --git a/chrome/browser/chrome_thread.cc b/chrome/browser/chrome_thread.cc index b8421b8..9c0d10c 100644 --- a/chrome/browser/chrome_thread.cc +++ b/chrome/browser/chrome_thread.cc @@ -9,7 +9,6 @@ static const char* chrome_thread_names[ChromeThread::ID_COUNT] = { "Chrome_IOThread", // IO "Chrome_FileThread", // FILE "Chrome_DBThread", // DB - "Chrome_HistoryThread", // HISTORY }; Lock ChromeThread::lock_; @@ -18,7 +17,6 @@ ChromeThread* ChromeThread::chrome_threads_[ID_COUNT] = { NULL, // IO NULL, // FILE NULL, // DB - NULL, // HISTORY }; ChromeThread::ChromeThread(ChromeThread::ID identifier) -- cgit v1.1