Comment #5 on issue 21377 by [email protected]: Crash - getVarint http://code.google.com/p/chromium/issues/detail?id=21377
With Scott we sat down and looked a this for a while. The history db is corrupted and the FTS2 code does not cope well with it on release. In this particular case we have the db (\User Data\Default\History Index 2009-06) > sqlite3.exe "User Data\Default\History Index 2009-06" SQLite version 3.6.17 sqlite> pragma integrity_check; *** in database main *** Page 1545 is never used Page 1546 is never used wrong # of entries in index sqlite_autoindex_pages_segdir_1 The pages_segdir is corrupted according to the auto index. Lets check: sqlite> select level,idx from pages_segdir where level=0; 0|0 0|5 0|6 0|7 0|8 0|9 0|10 0|11 0|12 0|13 0|14 0|15 This is missing 4 entries: 0|0 0|1 <=== 0|2 0|3 0|4 <=== 0|5 0|6 0|7 0|8 In fact, when you don't use the 'where' clause and thus you don't use the index we see: sqlite> select level,idx from pages_segdir; .... 1|5 1|6 0|0 0|6 0|7 0|8 0|9 0|10 0|11 0|12 0|13 0|14 0|15 Missing 0|5 as well. It is not possible at this time to know how the db got corrupted. -- 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 -~----------~----~----~----~------~----~------~--~---
