Comment #6 on issue 21377 by sh...@chromium.org: Crash - getVarint http://code.google.com/p/chromium/issues/detail?id=21377
Based on the integrity_check output, my suspicion is that the database is a mix of pages which are individually not corrupt, but which are corrupt when taken together. This can happen if, for instance, an interior node is updated to reference a different page which is not updated (that page could be an older page from the same tree, or a page from some other tree, etc). THAT should only be possible if you have a power-down event and the disk cache hadn't been fully flushed. The "Things that can go wrong" section at http://www.sqlite.org/atomiccommit.html discusses this kind of thing. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
