[chromium-dev] Re: found corrupted db

2009-09-10 Thread cpu
The plot thickens, the main history db is also corrupted: D:\test\corruptdbsqlite3.exe zzz\User Data\Default\History SQLite version 3.6.17 Enter .help for instructions Enter SQL statements terminated with a ; sqlite PRAGMA integrity_check; rowid 40017 missing from index visits_time_index rowid

[chromium-dev] Re: found corrupted db

2009-09-10 Thread Peter Kasting
On Wed, Sep 9, 2009 at 9:21 PM, Scott Hess sh...@chromium.org wrote: What's puzzling is how I know this, but we still see the crash. I'm pretty sure we fixed something or other around this. That was a year or more back, though, so maybe I'm not remembering right. Regardless, best-case

[chromium-dev] Re: found corrupted db

2009-09-09 Thread Scott Hess
fts uses what is effectively a form of compression for the index, so most any stream of data will decode at some level. My bet in this case is that the segdir is referencing a segment block which doesn't exist, so someone inappropriately tries to decode NULL. From what I recall of debugging