Comment #16 on issue 15261 by [email protected]: Crash in history::TextDatabase::GetTextMatches http://code.google.com/p/chromium/issues/detail?id=15261
At this time, I am unaware of any sqlite-internal cause of corruption. Doesn't mean it's not possible, of course! We discovered with Gears that when you run database code on millions of independent machines, you'll get a certain amount of corruption which does not have a good explanation like "This line of code is wrong". There's lots of code in there to make things best effort, but when you have laptops losing power at the wrong time, cosmic rays, and memory stompers in the program SQLite is embedded w/in, you will get a certain amount of corruption which is essentially sourceless, and the best solution is to detect it and take appropriate action (which often enough is to delete the database, though in some cases you may be able to design formats to let you recover some data). Unfortunately, fts is a bit less robust than SQLite core at detecting corruption. -- 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 -~----------~----~----~----~------~----~------~--~---
