Maybe we could also make Chromium more resilient against corrupted profile? We already have tools like stress_cache. There could be another tool, which would launch Chrome, randomly perform several actions, close it, randomly corrupt profile and launch it again. But I don't know for example how sqlite behaves when its database is corrupted (although it seems that crash is never a good idea). Paweł
On Fri, Mar 6, 2009 at 07:39, Finnur Thorarinsson <[email protected]>wrote: > I suspect this is like crashes due to memory corruption: It won't do much > good to stare at the call stack at the time corruption was detected; we need > to know the stack at the time corruption occurred (assuming this is Chrome > that is corrupting the profile). > For memory corruptions we have gflags; I wonder if there is something in > SqlLite that can help us here? > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
