Comment #39 on issue 9952 by [email protected]: Crash -
net::HttpCache::DeactivateEntry(net::HttpCache::ActiveEntry *)
http://code.google.com/p/chromium/issues/detail?id=9952
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=23344
------------------------------------------------------------------------
r23344 | [email protected] | 2009-08-13 12:45:31 -0700 (Thu, 13 Aug
2009) | 26 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/branches/195/src/net/disk_cache/backend_unittest.cc?r1=23344&r2=23343
M
http://src.chromium.org/viewvc/chrome/branches/195/src/net/disk_cache/entry_impl.cc?r1=23344&r2=23343
M
http://src.chromium.org/viewvc/chrome/branches/195/src/net/disk_cache/entry_impl.h?r1=23344&r2=23343
M
http://src.chromium.org/viewvc/chrome/branches/195/src/net/disk_cache/entry_unittest.cc?r1=23344&r2=23343
Merge 22637 - Disk Cache: Don't depend on the backend being enabled to
be able to return the key of an open entry.
Whenever a critical corruption is detected by the disk cache,
the backend disables itself and starts failing all requests
until it's able to recreate the backing store.
Key's longer than 928 bytes are not stored inside the entry
itself, so a file object is required to access them. The backend
will reject any request for a file object after it is disabled,
so a user's request for the key of an open entry will also
fail.
Now we keep a pointer to the related file object (if needed) so
that we don't have to ask the backend for it when the user
requests the current key.
BUG=9952
TEST=unittest
Review URL: http://codereview.chromium.org/165030
[email protected]
Review URL: http://codereview.chromium.org/164503
------------------------------------------------------------------------
--
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
-~----------~----~----~----~------~----~------~--~---
