Disable ProfileKeyedServices on import process by default.

chrome/browser/webdata/web_data_service.cc

Index: chrome/browser/webdata/web_data_service.cc
diff --git a/chrome/browser/webdata/web_data_service.cc b/chrome/browser/webdata/web_data_service.cc
index f36d92a52e76f007b1fbb7b57c1186bcf0f1580f..05dd5f25797bdf6efc697f5621fbfe9eee7ebd8d 100644
--- a/chrome/browser/webdata/web_data_service.cc
+++ b/chrome/browser/webdata/web_data_service.cc
@@ -90,7 +90,7 @@ WebDataService::WebDataService()
   // WebDataService requires DB thread if instantiated.
   // Set WebDataServiceFactory::GetInstance()->SetTestingFactory(&profile, NULL)
   // if you do not want to instantiate WebDataService in your test.
-  DCHECK(!ProfileManager::IsImportProcess(*CommandLine::ForCurrentProcess()));
+  CHECK(!ProfileManager::IsImportProcess(*CommandLine::ForCurrentProcess()));

[Peter Kasting, 2013/02/22 21:34:55]

CHECK means "Chrome has to crash immediately if this assertion fails, because we
are about to have a security exploit"; or "temporarily changed this to CHECK to
try and track down a bug".  Are those really what you mean?  If so, please add
an appropriate comment.  Otherwise, I don't think we should be using CHECK.

Also please see my comment on your last code review here.

   DCHECK(BrowserThread::IsWellKnownThread(BrowserThread::DB));
 }