AppCache: Run a quick integrity check on the sqlite database when opening.

chrome/browser/history/thumbnail_database.cc

Index: chrome/browser/history/thumbnail_database.cc
diff --git a/chrome/browser/history/thumbnail_database.cc b/chrome/browser/history/thumbnail_database.cc
index 46a182da1aa592040761854301e31d3b8fe85f44..4662ae2c6d0e76cacacf798f3ea91d2601e7e759 100644
--- a/chrome/browser/history/thumbnail_database.cc
+++ b/chrome/browser/history/thumbnail_database.cc
@@ -140,7 +140,7 @@ void ReportCorrupt(sql::Connection* db, size_t startup_kb) {
     std::vector<std::string> messages;
 
     const base::TimeTicks before = base::TimeTicks::Now();
-    db->IntegrityCheck(&messages);
+    db->FullIntegrityCheck(&messages);

[michaeln, 2013/12/09 19:15:51]

ooops, have to check the return value here

[Scott Hess - ex-Googler, 2013/12/09 20:27:27]

FYI, IntegrityCheck() was only added for this code to build fake-crash-dump
diagnostics.  So the API may not be anything like what a real client might want.

IMHO, nobody but diagnostics tools are going to want the actual messages.  I
think it would be perfectly fine to shift your new changes towards an API with a
bool return and no messages, and WARN_UNUSED_RESULT as appropriate.

     base::StringAppendF(&debug_info, "# %" PRIx64 " ms, %" PRIuS " records\n",
                         (base::TimeTicks::Now() - before).InMilliseconds(),
                         messages.size());