CCing a couple people from chrome/browser/browsing_data/OWNERS (Though maybe this should go to a settings owner?  No idea who owns thus stuff)

I think it's worth noting we can't really guarantee anything here, unless we don't save cookies on disk at all when that option is enabled, which would be a pretty big change (And when what do we do when the option is toggled on/off at runtime?  Ick).

This is something worth looking into, although I must reiterate mmenke@'s assessment. Once we save something to the disk, it's difficult to guarantee that we'll succeed to delete it.

Perhaps we could have some kind of mechanism at startup that audits cookies which weren't deleted on shutdown and tries to delete them again. But I'm not that familiar with the area, I think bauerb@ will be.

Otherwise, I can only recommend Incognito if you need to be sure that cookies (and other data) will be deleted at the end of the session.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tentatively assigning to dullweber@, who's been investigating when this could happen and if it does often.