| commit | 2f626ee3362fbda3404dc720c681afb8647f9323 | |
| author | jsbell@chromium.org <jsbell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 31 Oct 2013 01:36:56 +0000 (31 01:36 +0000) | ||
| committer | jsbell@chromium.org <jsbell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 31 Oct 2013 01:36:56 +0000 (31 01:36 +0000) | ||
| tree | aba7dad15783237eabb32091c01c88c2b0223ea9 | treesnapshot (tar.gz zip) |
| parent | c078461f8a6d45304f0edd5dacf10aa7074270e6 | commitdiff |
IndexedDB: Close backing store after a failed write
A failed write by leveldb can indicates either a transient I/O error by the foreground thread or that the background compaction thread has hit an error (I/O or corruption) which will make all future operations fail.
In lieu of being able to distinguish these for now, treat the write operation as fatal and force-close the backing store so that if the error was transient the store is not wedged until a browser restart. A well-behaved web app would be able to detect the close and re-open the connection.
BUG=251870
Review URL: https://codereview.chromium.org/48833005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231974 0039d316-1c4b-4281-b951-d872f2087c98
A failed write by leveldb can indicates either a transient I/O error by the foreground thread or that the background compaction thread has hit an error (I/O or corruption) which will make all future operations fail.
In lieu of being able to distinguish these for now, treat the write operation as fatal and force-close the backing store so that if the error was transient the store is not wedged until a browser restart. A well-behaved web app would be able to detect the close and re-open the connection.
BUG=251870
Review URL: https://codereview.chromium.org/48833005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@231974 0039d316-1c4b-4281-b951-d872f2087c98