There are occasionally bugs filed against Chrome that come down to cookies either existing where they shouldn't (session cookies after a restart) or not existing where they should (e.g. login cookies expected to persist over a shutdown as noted in issues 795827 and 794453 ). The network stack has no logging that I can see in either cookie_monster.cc (the default in-memory cookie store) or sqlite_persistent_cookie_store.cc (the on-disk persistent cookie store). There should be enough logging in those two areas that a netlog dump could be used to help debug problems like the ones described above.
This logging should specifically be able to indicate when cookies are added or deleted, and by what user initiated mechanism (web page visit, shutdown, startup, browsing data remover, eviction).
Obviously, this logging should only be done if the "include cookies and credentials" box is checked for netlog capture.
+mkwst@ FHI.
Comment 1 by mmenke@chromium.org
, Jan 16 2018