Comment #15 on issue 15261 by [email protected]: Crash in history::TextDatabase::GetTextMatches http://code.google.com/p/chromium/issues/detail?id=15261
Thanks for the info guys. For clarification, we are seeing crashes on Linux that could _possibly_ be caused by out of order offsets. I was confused by the test which seemed to imply that out of order offsets within a document are ok. I'll fix the unittest and add CHECKs to verify whether or not this is indeed the cause of the out of range exceptions. shess: When you say the most likely cause is undetected corruption, how would the history database get corrupted in this way? Is it possible that it's due to the chromium use of sqlite, or is it likely caused by external factors outside of chromium's control (say, a user mucking around with the database file on disk). -- 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 -~----------~----~----~----~------~----~------~--~---
