On Fri, Mar 6, 2009 at 9:33 AM, Brett Wilson <[email protected]> wrote: > Getting the database has helped in a few cases where it turned out some > assumptions were being violated, but if the sqlite data structures are > corrupted, getting the DB has never been helpful to diagnose the root cause. > > It might help us make sqlite not crash for these types of corruption, > though. > > I think we should install an exception handler on the DB threads, and if we > get two crashes in a row from sqlite, recreate the DB.
Yep. This would be nice. If these crashes are really this frequent, perhaps we should move the db out of the browser process. Or perhaps we could simply have an out of process validator that we could run if we got a single browser crash from sqlite. Erik > Brett > > On Mar 6, 2009 9:19 AM, "Erik Kay" <[email protected]> wrote: > > > One thing that would help is if some of the users who are running into > this would be willing to share their whole profile with us. > > While our best guess is that this is sqlite corruption, we don't know > for sure. Even if it is sqlite corruption, having the specific db > might help us figure out how to more reliably detect it. > > Erik > > On Thu, Mar 5, 2009 at 10:39 PM, Finnur Thorarinsson <[email protected]> > wrote: > I suspect this... --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
