Issue 2906: Cookie expiry code throws away valuable cookies (up limits,
change to last-accessed)
http://code.google.com/p/chromium/issues/detail?id=2906
Comment #33 by [EMAIL PROTECTED]:
I just had some cookies deleted, so I immediately checked my cookie store,
and found
I had 1016 cookies. I strongly suspect the expiry policy is to blame.
I think we have to fix expiry to be last-accessed. We should also consider
increasing our cookie limits; what are the disk, memory, startup time, etc.
ramifications of doing this? Can we make some test builds with doubled,
quadrupled,
etc. limits, give them profiles stuffed dull of bugs cookies and see what
the perf
effects are?
This doesn't change my desire to add some UMA data about cookies.
CCing mal because I don't know how else to nominate for 1.0. This could
probably
miss the 1.0 cut if it had to, but it's pretty supremely annoying.
Issue attribute updates:
Summary: Cookie expiry code throws away valuable cookies (up limits,
change to last-accessed)
Cc: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
--
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
-~----------~----~----~----~------~----~------~--~---
