Issue 3770: Crash after 1 minute http://code.google.com/p/chromium/issues/detail?id=3770
Comment #14 by [EMAIL PROTECTED]: Thanks! That was the solution and I can now see the crash. This also makes more sense. We start archiving old history after one minute, so Archived History being corrupted would definitely cause this. This database seems corrupt in a very unusual way. The data is itself OK, but the index is corrupt. This means when we look up one particular URL "http://exchange.movecrm.com.br/exchange/leonardo.lopes/?cmd=galfind&US=M"; it actually thinks it's there but has no data. This only causes a crash because the code that reads URLs out of the database expects the pointer to be non-NULL, which is a bug. The bug is easy to fix, and it should make this database not crash. But the database is basically corrupt and so other weird things could happen. Issue attribute updates: Status: Started -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to chromium-bugs@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
