I am sorry you lost your cookies.  I assure you, we're not deliberately deleting all your cookies.

Please do try to be respectful and constructive in your posts - See Chrome's code of conduct here:  https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md

Also sorry to hear you lost your cookies.

From the description I would guess your profile directory got corrupted or deleted on disk. Not sure that there is anything we can do here (and not really an Internal>Network>Cookies issue, more likely a profile issue).

Chrome's cookies are stored in a sqlite file at:

<user-data-dir>/Default/Cookies

Where <user-data-dir> is one of these:

[Chrome Stable]: ~/.config/google-chrome
[Chrome Beta]: ~/.config/google-chrome-beta
[Chrome Dev]: ~/.config/google-chrome-unstable
[Chromium]: ~/.config/chromium

I would start by looking at each of those directories and see if you have Default/Cookies. Even if the profile doesn't load, if you can get the Cookies file you can copy it over to a new profile.

If you have a Cookies file and aren't sure what is in it, you can dump it with:

$ sqlite3 Cookies .dump

Hope that helps.

> From the description I would guess your profile directory got corrupted or 
> deleted on disk. Not sure that there is anything we can do here

I think what you should do is find the bug that causes the profile directory to get corrupted so often, and fix it.
Until then, I think this bug report should be reopened as I have observed this issue quite a lot of times.

Why the fuck is this still WontFix?

Happened again.

Why the fuck don't you reopen this issue??

> Not sure that there is anything we can do here

There certainly is something you can and MUST do: manage the profile in a more robust way, so it doesn't get corrupted or wiped out so easily. I get this issue randomly every once in a while.

Sorry for the trouble.  Did you get the "profile I corrupted" warning again? 
I don't actually know what causes that (not my area..); the cookie store itself is just an SQLite database, so that ought to be pretty robust (though the encryption can be a weak point sometimes).

If your problem is just with cookies... well, if you still have the process running, could you perhaps take a look at chrome://histograms and see if there any entries for Cookie.LoadProblem, Cookie.CommitProblem, or Sqlite.Error.Cookie?

> Did you get the "profile I corrupted" warning again? 

No.

> If your problem is just with cookies...

It's the only thing I noticed that was gone.

> if you still have the process running

No, I don't.