Closed Bug 583568 Opened 14 years ago Closed 14 years ago

Cookies deleted via preferences menu are not removed from cookies.sqlite database

Categories

(Core :: Networking: Cookies, defect)

defect
Not set
major

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- final+

People

(Reporter: wgianopoulos, Assigned: dwitte)

References

Details

(Keywords: regression)

If from the Privacy preferences pane, I remove some cookies, they do not appear to be removed from the database. Steps to reproduce. 1. In the Privacy preferences pane click on "remove individual cookies". 2. Remove one or more cookies that will not be re-created via some other activity your browser or any extension might periodically be refreshing. 3. Close the preferences panel. 4. Reopen the preferences privacy panel. 5. Click on "remove individual cookies" and verify that the cookies you removed above no longer appear. 6. exit the browser. 7. re-launch the browser using the same profile. 8. from the preferences privacy panel click on "remove individual cookies" 9. Notice that the cookies you removed above are listed once again. I believe this is the root cause of the duplicate cookie issue which is causing people log-in problem with forums, gmail, google reader, etc.
Summary: Cookies deleted via preferences menu are not removed form cookies.sqlite database → Cookies deleted via preferences menu are not removed from cookies.sqlite database
blocking2.0: --- → ?
The patch on bug 572223 was just backed out. As and when there's a new build available, could you check and see if this still happens? (I guess you may need start by getting rid of the cookie database that's got into a mess)
After step 1, in the pref panel, do you see just one copy of each cookie listed? Or several? Note: it's important whether this occurs without closing the browser -- i.e. step 0 should be "clear cookies and start the browser, then browse around until you notice the bug". If it's one, that means the in-memory table is fine, and just the sqlite db contains the duplicates. If it's more, that means both do. I think it's the latter, which narrows the bug down to a regression in the in-memory handling itself.
(Please test this on your current build, not tonight's nightly, since it's been backed out!)
(In reply to comment #2) > After step 1, in the pref panel, do you see just one copy of each cookie > listed? Or several? Note: it's important whether this occurs without closing > the browser -- i.e. step 0 should be "clear cookies and start the browser, then > browse around until you notice the bug". I was testing this with a website I have not visited in quite some time. The site sets 2 cookies and I see only one copy of each cookie. I then deleted both of these cookies via the gui and the display then indicated that they were deleted from the in-memory table However the next time I launched the browser, both cookies were back even though I had still not visited this site, so it would seem that the cookies were never removed from the sqlite db. SO, the duplicates come for sites like Google where i try to log in and can't so I remove all the Google cookies, which evidently only removes them from the in-memory table and then i log in to Google creating all the cookies. Since the database ones were never deleted and the newly crated ones get added, the next time I launch the browser there are duplicates. The next time i try to log in I have to remove them again and upon the next launch I have triplicates.
OIC. This is not quite so simple. I am unable to duplicate this issue with a clean profile. Perhaps the sqlite DB needs to already be corrupt for this to occur.
Fixed per bug 572223.
Assignee: nobody → dwitte
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
blocking2.0: ? → -
blocking2.0: - → final+
You need to log in before you can comment on or make changes to this bug.