Issue 3019: Improper timestamps on the disk cache.
http://code.google.com/p/chromium/issues/detail?id=3019
Comment #3 by [EMAIL PROTECTED]:
doh!. You are right, I was looking at the wrong place on the implementation.
Time::Now does indeed return the system time, and the numbers coming from
the cache
make sense.
The issue came from some histogram data that shows that 4065 entries older
than 10000
hours were deleted, and that is just plain wrong! (not to mention 274
entries between
5961 hours and 10000). I don't see how we can have such numbers giving that
the data
for the histogram is just (Time::Now() - entry->GetLastUsed()).InHours(). I
guess
I'll have to keep looking...
Issue attribute updates:
Status: Invalid
--
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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---
