I think the "bug" here is that the cookies page fetches the favicon of each tld you've got a cookie for, which can be many tens of thousands. Hopefully #39 follows up here.

I don't think original request is saying that rendering cookies in DevTools is slow.

@2 Correct, I'd made an incorrect summary line. Updated summary, (wdyt?)

I still can't parse the "Not sure if related (my guess it is). When monitoring the network, it seems for every site that you have cookies, there is a network communication. Why? Cookies are local!". Do you understand what the scenario is? We can't do anything without the scenario / repro. Over to you for clarification.

I guess you didn't read my comment (#1); the scenario is that if you view all your chrome cookies (eg: by navigating through the menus to chrome://settings/siteData ), it fetches a fresh favicon for each tld (which may be tens of thousands or more). That's a problem. 

I have a screenshot of something like the original. Not sure it's touching the network, but I can't actually view all the cookies anyway. Page never finishes rendering because there are so many. (I think there's another bug already covering that issue)

See attached shots

Deleted: Screenshot_20171130_185231.png 216 KB

	Screenshot_20171130_185231.png 216 KB View Download

Deleted: Screenshot_20171130_185340.png 33.0 KB

	Screenshot_20171130_185340.png 33.0 KB View Download

@orangewinds: what exactly is your concern about? the page loads images, network panel shows that. I don't see anything special / wrong about it...

@1 and @7 I'm not sure if this is the primary concern, but how long (and how much bandwidth) does it take to connect to a few thousand sites and get their favicon? If that amounts to almost-nothing then I'd agree this bug should be marked WontFix. If it's enough to cause the UI to lag (or be less than snappy) then that detracts from an excellent experience and should be addressed. (IMO of course).

There must be some misunderstanding - devtools does not load these images, the inspected page does. Did you mean to file this bug against the chrome://settings/siteData owners? That's different than DevTools...

julien.henry@ and orangewinds@,

Thanks for reporting this issue and following up on it. I'm marking this* bug WontFix because there is not enough clear separation** from the other (fixed) bug (about sideData).

If the issue persists, please create an entirely new bug for the siteData page (only) or the dev tools (only) and/or an easily reproducible example.




*I mean that this particular report is not going to be addressed, not that the bug can't be fixed. We don't have enough clarity on this bug report (and I believe adding to this report will not get us that clarity).

**In hindsight, it would have been better if I made a new bug with a repro example rather than this bug which links to another bug. Sadly I don't have a repro example to make a new report with (that's where I'd like your help).