Comment 44 for bug 457791

(In reply to comment #35)
> (In reply to comment #21)
> > I can reproduce this issue quickly and easily on my system.
> >
> > Steps to reproduce:
> >
> > 1) Either start from a new profile, or do a "Clear Recent History" with
> > time range "Everything" and at least the "Cookies" box checked
> > followed by running "sqlite3 cookies.sqlite vacuum".
> >
> > 2) Run "strings cookies.sqlite | grep -i google", and observe that no
> > results appear.
> >
> > 3) Open Firefox, and visit google.com. Close Firefox.
> >
> > 4) Run "strings cookies.sqlite | grep -i google", and observe that some
> > results appear, as expected.
> >
> > 5) Open Firefox. Do a "Clear Recent History" with time range
> > "Everything" and at least the "Cookies" box checked. Close
> > Firefox.
> >
> > 6) Run "strings cookies.sqlite | grep -i google", and observe that the
> > results from step 4 still appear, despite having cleared cookies.
>
> Have you also tested this with some other domain than google.com?
> The problem is that if between steps 5 and 6 there were some hidden connections
> to Google (eg. related with so-called "safebrowsing"), then the google cookie
> "magically" reappears.

Yes, I've confirmed it with domains other than google.com. And, I also confirmed when I saw the data in cookies.sqlite that the moz_cookies table had no rows, thus indicating no cookies present; the data appearing in cookies.sqlite thus represents random garbage not deleted from the file.