Comment #10 on issue 15261 by willc...@chromium.org: Crash in history::TextDatabase::GetTextMatches http://code.google.com/p/chromium/issues/detail?id=15261
So, the actual crash is on a SIGABRT from a string out of range exception in Snippet::ComputeSnippet(). AFAICT, the only string indexing we're doing is document.substr(). Having looked at this, I'm not sure it's a corrupt history database. We're doing a fts select query, and sqlite is returning the offsets of the matches. Either the offsets are wrong, or we have a bug in how we handle the offsets. I'm going to add some CHECKs to see which it is. -- 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 -~----------~----~----~----~------~----~------~--~---
