kailoran@ - Thanks for filing the issue...!!

Could you please provide a screen cast for better understanding of the issue.
This will help us in triaging the issue further.

Thanks...!!

Have same issue, cookies are not saved after restarting Chrome. Issue reproduces on dev (70.0.3538.9) also. Tried on 68 with clean profile - works as expected on same site (i.e. cookie persists)
Attaching screencast

Deleted: chrome.mov 9.5 MB

	chrome.mov 9.5 MB View Download

@krajshree I'm unable to cast anything since it happened exactly once, during an upgrade. I got logged out of everything. It seems different from what #4 mentions, things are fine for me now on 69, but the upgrade from 68 to 69 ate cookies.

Thank you for providing more feedback. Adding the requester to the cc list.

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

kailoran@ - As per comment #5, please let us know if the issue can be closed.

Thanks...!!

This is a report of a single instance of what looks to be a bug in some cookie database upgrade process that's not as robust as it should be. Why should it be closed?

Thank you for providing more feedback. Adding the requester to the cc list.

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

Unable to reproduce the issue on win-10 using chrome reported version #69.0.3497.92.
Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. On chrome #68.0.3440.106, logged into gmail.com and checked for cookies at chrome://settings/content.
2. Relaunched chrome and after the version got updated to 69.0.3497.92, checked the cookies and observed that none of the cookies were gone.

kailoran@ - Could you please check the attached screen cast and please let us know if anything missed from our end. Also if possible please provide any sample url where is issue is getting observed.

Thanks...!!

Deleted: 881683.mp4 2.5 MB

	881683.mp4 2.5 MB View Download

The screencast is okay, if a bit overkill for what should be clear from a text description IMO :) In my case, let's say I logged in to gmail before noticing the issue, so the cookies tab had some google cookies, but _everything else_ there was gone (I was logged in to multiple sites on that profile). So any url, essentially.

Thanks for checking. I don't expect the issue to have a trivial reproduction scenario, it looks like a random corruption that's not handled gracefully; so this is a data point for the migration not being 100% robust.

Thank you for providing more feedback. Adding the requester to the cc list.

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

To those for whom the issue reoccurs every time: after a couple of minutes of using chrome, could you go to chrome://histograms and see if there are any entries for Cookie.LoadProblem, Cookie.CommitProblem, and SQLite.Error.Cookie, and if so, paste any that exist here?

As for the one time thing on upgrade: there shouldn't be an upgrade process between 68 and 69, the format is identical...

morlovich@: thanks for the response. So I guess things just exploded somehow in between the couple of restarts in and out of safe mode I did around the upgrade.

Again unable to reproduce the issue on win-10 using chrome reported version #69.0.3497.92. Hence, removing the Needs-Bisect label and requesting some one from Internals>Network>Cookies team to please have a look into the issue.

Thanks...!!

If there was no upgrade then I guess there's little that can be done here and it should be closed as not reproducible.

No cookie db upgrade and expected migration during the 68->69 upgrade that is.

As we are unable to reproduce the issue from our end (...as per C#10 & C#15) adding label "TE-NeedsTriageHelp" and requesting someone from the respective team to have a look into this and help in further triaging it.

Thanks!

With no repro and clues I think this should be closed.