chrome://net-internals/#sockets shows entries after browsing data deletion |
||
Issue descriptionChrome Version: (copy from chrome://version) OS: (e.g. Win10, MacOS 10.12, etc...) What steps will reproduce the problem? (1) Visit https://example.com (2) Close example.com (3) Delete cookies, cache and history What is the expected result? All traces of the visit to example.com should have been removed. What happens instead? The connection to example.com has been closed but chrome://net-internals/#sockets still shows an entry for ssl/example.com:443 with no connections.
,
Jul 6
The remaining entries still have an active socket after ClientSocketPoolBaseHelper::FlushWithError() has been called. The active socket is removed shortly after by ClientSocketPoolBaseHelper::ReleaseSocket but it doesn't remove the group. I created https://crrev.com/c/1127794 to fix this issue.
,
Jul 12
dullweber: Adding you to owner since it seems you are moving this forward based on #2. Feel free to move back to untriaged if I'm off base :) |
||
►
Sign in to add a comment |
||
Comment 1 by msramek@chromium.org
, Jul 6