Comment #6 on issue 9355 by [email protected]: Crash - disk_cache::EntryImpl::Update(disk_cache::EntryImpl *) http://code.google.com/p/chromium/issues/detail?id=9355
This is a crash that somehow bypasses the logic that detects "dirty" entries (entries that cannot be trusted because they are corrupt on disk, most likely due to a previous browser crash). I've found instances of this crash as far back as ver 1.0.154.46, but there is a clear jump in the number of crashes between ver 2.0.166.1 (r10169) and ver 2.0.167.0 (r10575): from about 0.017% of the total crashes to about 0.245%. The funny thing is that the only change on the disk cache on this revision range is changing the histogram names from wchar to char, so there is no real code change. So I'm still looking... -- 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 -~----------~----~----~----~------~----~------~--~---
