Open the LoginDatabase on the DB thread, not the UI thread.

components/password_manager/core/browser/login_database.h

Index: components/password_manager/core/browser/login_database.h
diff --git a/components/password_manager/core/browser/login_database.h b/components/password_manager/core/browser/login_database.h
index d348c26f13818c370614c9b57b75cd3f0601bf6e..bb74de5b03a8608526f5e6462d30c7325125bb67 100644
--- a/components/password_manager/core/browser/login_database.h
+++ b/components/password_manager/core/browser/login_database.h
@@ -102,6 +102,9 @@ class LoginDatabase {
   // whether further use of this login database will succeed is unspecified.
   bool DeleteAndRecreateDatabaseFile();
 
+  // Simulates a failure in the Init() method of any instance. Used for testing.
+  static void set_simulate_init_failure_for_testing(bool fail);

[Garrett Casto, 2015/01/14 08:50:22]

What do you think of instead of adding this field, to keep passing in a
LoginDatabase object where Init() hasn't been called. We can then use a test
only subclass where we override Init() to return false. This keeps test only
code out of the production class. The drawback is that we need to specify this
in the contract of the class that the object passed in has not been Init()'ed. I
think I slightly prefer that setup. What do you think?

[engedy, 2015/01/14 14:36:54]

Sounds great, actually, I did not like the current solution either.

+
  private:
   // Result values for encryption/decryption actions.
   enum EncryptionResult {