Closed Bug 6401 Opened 25 years ago Closed 25 years ago

cookies file grows like crazy - forever

Categories

(Core :: Networking: Cookies, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 2414

People

(Reporter: ramiro, Assigned: morse)

References

()

Details

start with an empty cookie file: rm -f ~/.mozilla/cookies goto www.yahoo.com, search for something there now is one yahoo entry on the cookies file exit the viewer and run it again goto another site that adds a cookie, say www.dejanews.com search for something, now look at the cookies file. the yahoo entry from above is DUPLICATED right before the new dejanews entries. exit the viewer and run it again goto a third site, say excite.com and do a search. look at the cookies file and notice how everything is duplicated again. after a while, the cookies file grows to megabytes and makes everything about the app unusable. this bug doesnt seem to happen on windows. i bet you have a misplaced #ifdef XP_PC somewhere.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
This is a duplicate of 2414. Don't be fooled by the wording on 2414 which talks about initial cookie file on mac -- read the report and see that it also covers the growing cookie file on unix. The code for all of this is inside of netlib (mkaccess.c). All that code is being completely thrown out to be replaced by necko. For that reason 2414 was marked as "wont-fix" *** This bug has been marked as a duplicate of 2414 ***
I will verify this as a dup although ramiro, I must admit I do not see this at all on Unix. My cookies file stays small and friendly - when I write a new cookie, it simply adds that one cookie to the file, there is no duplication. I did see it about a month ago.
Status: RESOLVED → VERIFIED
did you quit restart the the app ? where you using viewer or apprunner ?
apprunner, and I've been using the same cookie file for awhile (confirmed by checking time stamp that it's writing to the file). Strange.
ok, then this happens only in the viewer. thanks for confirming this.
Well that clarifies a lot of things. As discussed in report 2414, the problem did exist in unix apprunner and was happening because all initializations (at a higher level than cookies) were being done twice; this caused the cookies file to be read in twice and therefore every cookie was duplicated. Hubie's analysis and fix for that problem are described in 2414. So I'm guessing that Hubie's fix applied only to apprunner and a similar fix needs to be done for viewer. But are we really going to continue to maintain both apprunner and viewer, or is viewer being deprecated?
You need to log in before you can comment on or make changes to this bug.