Updates:
Summary: HTTP Requests do not finish loading properly (blank page),
need
to refresh page
Status: Untriaged
Comment #3 on issue 27324 by [email protected]: HTTP Requests do not
finish loading properly (blank page), need to refresh page
http://code.google.com/p/chromium/issues/detail?id=27324
Thanks for the debug information! This is very helpful! Here's the key
data from
the net-internals page:
http://code.google.com/p/chromium/issues/detail?id=16367
t=147371905: +URL_REQUEST_START [dt=445]
t=147371905: +HTTP_CACHE_OPEN_ENTRY [dt= 0]
t=147371905: -HTTP_CACHE_OPEN_ENTRY
t=147371905: +HTTP_CACHE_CREATE_ENTRY [dt= 0]
t=147371905: -HTTP_CACHE_CREATE_ENTRY
t=147371905: +HTTP_CACHE_WAITING [dt= 0]
t=147371905: -HTTP_CACHE_WAITING
t=147371905: +PROXY_SERVICE [dt= 0]
t=147371905: -PROXY_SERVICE
t=147371905: +SOCKET_POOL [dt= 31]
t=147371907: +SOCKET_POOL_CONNECT_JOB [dt= 29]
t=147371907: +HOST_RESOLVER_IMPL [dt= 0]
t=147371907: +HOST_RESOLVER_IMPL_OBSERVER_ONSTART [dt= 0]
t=147371907: -HOST_RESOLVER_IMPL_OBSERVER_ONSTART
t=147371907: +HOST_RESOLVER_IMPL_OBSERVER_ONFINISH [dt= 0]
t=147371907: -HOST_RESOLVER_IMPL_OBSERVER_ONFINISH
t=147371907: -HOST_RESOLVER_IMPL
t=147371907: +TCP_CONNECT [dt= 29]
t=147371936: -TCP_CONNECT
t=147371936: -SOCKET_POOL_CONNECT_JOB
t=147371936: -SOCKET_POOL
t=147372350: -URL_REQUEST_START
and
http://code.google.com/p/chromium/issues/detail?id=16367
t=147281622: +URL_REQUEST_START [dt=90285]
t=147281622: +HTTP_CACHE_OPEN_ENTRY [dt= 0]
t=147281622: -HTTP_CACHE_OPEN_ENTRY
t=147281622: +HTTP_CACHE_WAITING [dt= 0]
t=147281622: -HTTP_CACHE_WAITING
t=147281622: +HTTP_CACHE_READ_INFO [dt= 0]
t=147281622: -HTTP_CACHE_READ_INFO
t=147281622: +PROXY_SERVICE [dt= 0]
t=147281622: -PROXY_SERVICE
t=147281622: +SOCKET_POOL [dt= 35]
t=147281622: +SOCKET_POOL_CONNECT_JOB [dt= 35]
t=147281622: +HOST_RESOLVER_IMPL [dt= 0]
t=147281622: +HOST_RESOLVER_IMPL_OBSERVER_ONSTART [dt= 0]
t=147281622: -HOST_RESOLVER_IMPL_OBSERVER_ONSTART
t=147281622: +HOST_RESOLVER_IMPL_OBSERVER_ONFINISH [dt= 0]
t=147281622: -HOST_RESOLVER_IMPL_OBSERVER_ONFINISH
t=147281622: -HOST_RESOLVER_IMPL
t=147281622: +TCP_CONNECT [dt= 35]
t=147281657: -TCP_CONNECT
t=147281657: -SOCKET_POOL_CONNECT_JOB
t=147281657: -SOCKET_POOL
t=147371907: -URL_REQUEST_START
The order is from more recent to older. So, the second request is the
older one.
That's the one that froze up for 90 seconds, until croftjd refreshes and
issues the
second one. We can note that there is no bug in host resolution nor tcp
connect().
It's not clear at what point we get stuck. I'm not sure if it's a code bug
or a
network issue. I'm guessing we're getting stuck somewhere in
HttpNetworkTransaction,
but I can't tell. There are two things todo here.
First, @croftjd, thanks for the wireshark trace, but I need to see the
wireshark
trace from before you even try to issue the request. So if you can just
have
wireshark running and try to repro, that'd be great. A full wireshark
trace would
help immensely.
Second, Eric and I need to finish instrumenting the http stack with
LoadLog. There's
a big black hole after the TCP connect finishes, where we don't know where
the time
went. I'd like to know why we get stuck for 90 seconds after the TCP
connection.
Once we get the patches in, then we can have you croftjd us more
informative net-
internals traces.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
