Have you been having your brower’s cookies just seem to disappear when they didn’t used to (in say, Firefox 2)? A few others and I have noticed this, but we haven’t figured out what is up yet. After talking to Dan Witte, the cookie module owner, we still don’t know what’s up. However, if you’ve been seeing this strange and unsettling behavior, you can help us get to the bottom of it! Dan is looking for cookie logs to see if he can spot the bug. Here’s how you can help:
- Clear all of your cookies or start with a fresh profile.
- Enable cookie logging. If anyone knows how to do that on the mac, please add those instructions too!
- After you enable logging, start your browser, and use it normally. Whenever you think you lost a cookie, there are a couple of things you need to note:
- The site that you think lost the cookie.
- The day/time you lost the cookie.
Send that and your log to dwitte at gmail.com and hope for the best!
The more people on this, the more likely we are to find out what’s going on! Your help is greatly appreciated!
11 replies on “Cookie Monster Eating Your Cookies?”
I filed bug 403228 to provide a Mac version of the instructions. If it would be useful, it would be trivial for me to write an AppleScript applet that would automate those steps, too.
@Smokey
If it’s trivial, that could be rather helpful!
[…] Camino while rewriting the Firefox download manager and Gecko content handling last summer ) recently wrote about a problem plaguing trunk builds of Mozilla applications: cookies are mysteriously […]
I’ve been dealing with this for a long time now on Camino trunk:
https://bugzilla.mozilla.org/show_bug.cgi?id=395860
I’m currently running w/out Flash to see if that’s the issue.
In the event the trackback doesn’t work (which seems to be the case), I’ve got the AppleScript ready now and have a blurb about it here.
Thanks for posting about this; we have one Camino user who’s experiencing something like this, and our best guess was that the leaking Flash descriptors was causing it…,
Yes I have experienced that Mozilla is eating my cookies and have now enabled the cookie logging.
Most of the lines look like this:
0[3858f0]: RemoveExpiredCookies(): 0 purged; 1000 remain
why does it almost always say 1000 remain?
@Henrik
There is a limit on the number of cookies you can have, and that happens to be 1000.
We’ve figured out what the problem was – thanks to ispiked’s dedicated cookie logging, which generated multiple 300mb logs. :p
Thanks much sdwilsh and smokey for helping out! I’ll post a link to the bug once I file it…
filed as bug 403372, will get in a fix for the next beta!
I think we all hit bug:
https://bugzilla.mozilla.org/show_bug.cgi?id=403372
dont we?
[…] Calendar Cookie Monster Eating Your Cookies? […]