1. Does this happen when wikipedia page is previously open for hours, or is browser running without connecting to wikipedia?

2. Does it happen if you try open an incognito profile (this should establish a new connection)?

If it happens again, could you try to collect net log according to these instructions: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details

1. No wikipedia tab was previously open. So, new connection.
2. Incognito doesn't help, and restarting the browser also doesn't help.

Deleted: net-internals-log.json 171 KB

net-internals-log.json 171 KB View Download

Deleted: net-internals-log (1).json 90.2 KB

net-internals-log (1).json 90.2 KB View Download

Thank you for providing more feedback. Adding requester "mef@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

It looks like a connectivity issue, with SSL_CONNECT sending 208 bytes, but not receiving any response and timing out after 30 seconds. There is no HTTP/2 in use. This looks like some third party software is blocking the connection.

117545: SSL_CONNECT_JOB
Start Time: 2017-03-11 10:48:28.609

t=42321 [st=    0] +SOCKET_POOL_CONNECT_JOB  [dt=30003]
                    --> group_name = "ssl/en.wikipedia.org:443"
t=42321 [st=    0]   +SOCKET_POOL_CONNECT_JOB_CONNECT  [dt=30003]
t=42321 [st=    0]      TCP_CLIENT_SOCKET_POOL_REQUESTED_SOCKET
                        --> host_and_port = "en.wikipedia.org:443"
t=42321 [st=    0]     +SOCKET_POOL  [dt=2]
t=42323 [st=    2]        SOCKET_POOL_BOUND_TO_CONNECT_JOB
                          --> source_dependency = 117546 (TRANSPORT_CONNECT_JOB)
t=42323 [st=    2]        SOCKET_POOL_BOUND_TO_SOCKET
                          --> source_dependency = 117548 (SOCKET)
t=42323 [st=    2]     -SOCKET_POOL
t=72324 [st=30003]      SOCKET_POOL_CONNECT_JOB_TIMED_OUT
t=72324 [st=30003]   -SOCKET_POOL_CONNECT_JOB_CONNECT
                      --> net_error = -7 (ERR_TIMED_OUT)
t=72324 [st=30003] -SOCKET_POOL_CONNECT_JOB
117548: SOCKET
Start Time: 2017-03-11 10:48:28.611

t=42323 [st=    0] +SOCKET_ALIVE  [dt=30001]
                    --> source_dependency = 117546 (TRANSPORT_CONNECT_JOB)
t=42323 [st=    0]   +TCP_CONNECT  [dt=0]
                      --> address_list = ["91.198.174.192:443"]
t=42323 [st=    0]     +TCP_CONNECT_ATTEMPT  [dt=0]
                        --> address = "91.198.174.192:443"
t=42323 [st=    0]   -TCP_CONNECT
                      --> source_address = "0.0.0.0:0"
t=42324 [st=    1]   +SOCKET_IN_USE  [dt=30000]
                      --> source_dependency = 117545 (SSL_CONNECT_JOB)
t=42324 [st=    1]     +SSL_CONNECT  [dt=30000]
t=42324 [st=    1]        SOCKET_BYTES_SENT
                          --> byte_count = 208
t=72324 [st=30001]   -SOCKET_IN_USE
t=72324 [st=30001] -SOCKET_ALIVE

There are many different modules loaded in Chrome, could that have some effect?

Can you try to run Chrome with '--disable-extensions --disable-plugins' command line arguments and see if that helps?

Same thing.
After some time chromium gets connection timeouts while at the same time curl and another chromium instance under another user works fine.

There are is no firewall set up. iptables rules are empty.

Deleted: net-internals-log.json 132 KB

net-internals-log.json 132 KB View Download

Thank you for providing more feedback. Adding requester "mef@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

tinylord@ - thanks for another netlog! It does show the same pattern with SSL_CONNECT_JOB sending 208 bytes and not receiving anything back.

I'm adding SSL label to get it on the radar of SSL folks.

t=24433 [st=    0] +SOCKET_POOL_CONNECT_JOB  [dt=30003]
                    --> group_name = "ssl/en.wikipedia.org:443"
t=24433 [st=    0]   +SOCKET_POOL_CONNECT_JOB_CONNECT  [dt=30003]
t=24433 [st=    0]      TCP_CLIENT_SOCKET_POOL_REQUESTED_SOCKET
                        --> host_and_port = "en.wikipedia.org:443"
t=24433 [st=    0]     +SOCKET_POOL  [dt=2]
t=24435 [st=    2]        SOCKET_POOL_BOUND_TO_CONNECT_JOB
                          --> source_dependency = 7605 (TRANSPORT_CONNECT_JOB)
t=24435 [st=    2]        SOCKET_POOL_BOUND_TO_SOCKET
                          --> source_dependency = 7607 (SOCKET)
t=24435 [st=    2]     -SOCKET_POOL
t=54436 [st=30003]      SOCKET_POOL_CONNECT_JOB_TIMED_OUT
t=54436 [st=30003]   -SOCKET_POOL_CONNECT_JOB_CONNECT
                      --> net_error = -7 (ERR_TIMED_OUT)
t=54436 [st=30003] -SOCKET_POOL_CONNECT_JOB

7607: SOCKET
Start Time: 2017-03-14 17:30:31.025

t=24435 [st=    0] +SOCKET_ALIVE  [dt=30001]
                    --> source_dependency = 7605 (TRANSPORT_CONNECT_JOB)
t=24435 [st=    0]   +TCP_CONNECT  [dt=0]
                      --> address_list = ["91.198.174.192:443"]
t=24435 [st=    0]     +TCP_CONNECT_ATTEMPT  [dt=0]
                        --> address = "91.198.174.192:443"
t=24435 [st=    0]   -TCP_CONNECT
                      --> source_address = "0.0.0.0:0"
t=24435 [st=    0]   +SOCKET_IN_USE  [dt=30001]
                      --> source_dependency = 7604 (SSL_CONNECT_JOB)
t=24435 [st=    0]     +SSL_CONNECT  [dt=30001]
t=24435 [st=    0]        SOCKET_BYTES_SENT
                          --> byte_count = 208
t=54436 [st=30001]   -SOCKET_IN_USE
t=54436 [st=30001] -SOCKET_ALIVE

I have this issue too in github.com and python.com sites.
I attached printscreen of wireshark and chromium screen, in addition i attached wireshark log.

Thank you :)

Deleted: chrome_printscreen 51.9 KB

chrome_printscreen 51.9 KB View Download

Deleted: wireshark_printscreen 187 KB

wireshark_printscreen 187 KB View Download

Deleted: hex_tcp_stream_to_github.txt 8.1 KB

hex_tcp_stream_to_github.txt 8.1 KB View Download

I had the same problem on github site behind a corp proxy. Please check this: https://bugs.chromium.org/p/chromium/issues/detail?id=583021
It seems Chrome doesn't use the standard proxy, but WINHTTP proxy settings. this prevents it to verify EV certificates, so some sites  will load slowly.

To comment #10: Please file a new bug and attach a NetLog per these instructions.
https://dev.chromium.org/for-testers/providing-network-details