Some columns contain a primary field and a secondary field (Time and
Latency, for example). When viewing the Network table with large
resource rows both fields are shown; when using small resource rows
only the primary field is shown.
I ended up solving this issue by configuring ipv6 on my network (I had ipv6 disabled on my dhcp server). It seems that a lot of extensions attempt to contact ipv6 addresses on startup. Once those addresses were able to resolve using a working ipv6 connection, all my startup delay issues went away.
It seems just unchecking IPV6 on all of the network adapter properties solves the issue. I'll wait a couple days to see if the work around sticks but this has been a thorn in my side for some time now.
On Windows, try the following commands which may help:
ipconfig /flushdns
nbtstat -R
netsh winsock reset
netsh int ipv4 reset
netsh int ipv6 reset
netsh winsock reset will fix it for a short amount of time. This only seems to affect our Windows 7 computers and not our Windows 8 computers.
Temporary disable or uninstall anti-virus, firewalls and similar.
Try changing into different network (e.g. VPN or mobile hotspot) to see if the problem persist.
Debugging
Enable logging by running Chrome from the command-line with --enable-logging or --v=1 parameter.
Check if anything is happening by opening DevTools (Network and Console tabs).
Go to chrome://histograms to display stats accumulated from browser startup to previous page load (you may search for Delay or Throttle keywords).
Use chrome://tracing to record and debug any processing issues, then analyse the data, especially by checking the most consuming component which web browser was stuck at.
If none of above helps, please the bug report with details of the issue, ideally with attached trace_record.json.gz file generated at chrome://tracing while reproducing the problem.
Best Answer
I see your Filter tab is red, so there is no filtered data in it.
you should check if your Filter is selected suitable controls:
check
All
should be log the HTTP request right. if you checkDoc
,Manifest
, when you HTTP request, there maybe no logs.