diff options
| author | erikwright@chromium.org <erikwright@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-04 15:57:23 +0000 |
|---|---|---|
| committer | erikwright@chromium.org <erikwright@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-04 15:57:23 +0000 |
| commit | 42463cfc2579c54857ef43300cc55af08471a43f (patch) | |
| tree | 2555b868dc4c0731f285743deb5b020aed95c7f4 /ash | |
| parent | 62727eb12896e120ded3ce025db05ca68e592307 (diff) | |
| download | chromium_src-42463cfc2579c54857ef43300cc55af08471a43f.zip chromium_src-42463cfc2579c54857ef43300cc55af08471a43f.tar.gz chromium_src-42463cfc2579c54857ef43300cc55af08471a43f.tar.bz2 | |
Reinitialize the cookie database if the meta table gets corrupted.
This has been shown to occur in the wild. At the moment users in this situation will simply get a failure to load or persist cookies (though cookies will work within the current session). After this change, users will see their Cookie database wiped out and reinitialized, but loading and persisting should work going forward.
A histogram tracks how often this scenario is detected - it should probably spike as this is rolled out to new channels and then taper off (hopefully approaching 0).
This is a minimal version with the hopes of being eligible for patching into M18. The preferred long-term version is here: http://codereview.chromium.org/9567022/
TBR=shess
BUG=111376
TEST=unit_tests --gtest_filter=SQLitePersistentCookieStoreTest.TestInvalidMetaTableRecovery
Review URL: http://codereview.chromium.org/9602001
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@124899 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ash')
0 files changed, 0 insertions, 0 deletions