Closed Bug 643762 Opened 14 years ago Closed 14 years ago

Out of date cookies not removed in FF4

Categories

(Core :: Networking: Cookies, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: rvjanc, Unassigned)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0) Gecko/20100101 Firefox/4.0 I used an empty new profile to test this in FF4. 1. I set the preferences to: Use custom settings for history -> Accept cookies from sites -> Keep until they expire 2. Went to a site that sets a cookie that, after logging out will expire in 30 minutes. 3. Quit FF 4. Opened FF one hour later, cookie still there 5. Quit FF 6. Opened FF again and cookie is still there I performed the same test in FF3.6.13 and the cookie is removed. Reproducible: Always Actual Results: Out of date cookies in FF4 are not removed Expected Results: Out of date cookies should be removed when FF is quit Using FF4 on OSX 10.6.6
Component: General → Networking: Cookies
Product: Firefox → Core
QA Contact: general → networking.cookies
Version: unspecified → Trunk
Expired cookies are not continuously removed from the database (that would cause many write operations, spinning up the hard disk on an idle laptop for instance). They're not even removed when the application starts up (that was removed in bug 576347 to speed up startup). When the cookie is found during a read operation, it will not be used of course. There is a PurgeCookies routines at <http://mxr.mozilla.org/mozilla-central/source/netwerk/cookie/nsCookieService.cpp#2729>, but it will only clean the database once in a while (10% over the size limit). Bug 576347 is an attempt to have a smarter routine that might run once per day when the browser is idle or something.
Invalid per comment 1.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.