Google Chrome page load problem (ERR_TIMED_OUT)

09
2013-08
  • nimcap

    I am having this annoying problem with Google Chrome, although I used to love Chrome I will switch to Firefox if the problem persists.

    Sometimes while loading a page Chrome fails and displays ERR_TIMED_OUT error.

    enter image description here

    This does not occur every time, in average out of 10 page loads 1 fails. When I hit refresh a couple of times, it will load eventually.

    I am using Firefox for a couple of hours now and it seems to work fine.

    So far I tried these: clearing cache, switching user profiles, disabling DNS prefetching, disabling detection of connection settings automatically in IE (yes, I don't know why this is here, but I remember having the same problem a few years ago and this worked). I run out of ideas.

    How can I prevent this error from happening? Or at least how can I trace the source of this error?

    • Answers
    Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

    Related Question

    ubuntu - Google Chrome can't load too many tabs together!
  • tapan

    This is an annoying problem that I face and friends of mine agree to this too. When using a site like Digg I tend to browse the page and open a lot of tabs simultaneously before reading each tab individually. Now what happens is, when there are 4-5 or more tabs loading up, all of them just stop loading.I can still see that annoying circle rotating (which means it is trying to load) but nothing happens. I have to stop the load and then refresh one tab at a time to see these pages. I never faced these problems on firefox or opera. What can the possible reasons for this be and how do I overcome this issue ? I'm using Ubuntu 10.04 and my Chrome Version is 5.0.375.55. PS: I use the internet from behind a proxy server at my college. I wonder if that could cause these problems. My friends in college also face the same problem.


    • Related Answers
  • Dan

    Sounds like they are limiting the number of open connections you can have. This is probably designed to prevent people from using bit torrent (which usually requires a large amount of really slow connections, but can really add up).

    If my guess is correct, you should have this same problem using firefox. Also, when chrome is currently maxed out, if you try to open firefox it should let you open at most 1-2 web pages.

    EDIT: I've been searching for a way to limit the number of tabs that load at a time to prevent them from stopping. The only solution I have found is in firefox by limiting the network.http.max-connections and network.http.max-connections-per-server variables (which was suggested here). This will make it so only a certain number of tabs load at a time, but it will hopefully prevent them from stopping altogether like it has been for you. Perhaps start off by limiting network.http.max-connections (type about:config into your firefox browser) to 3 or 4 and seeing if that works. You can play around with tweaking the value to see what works best for you. I haven't been able to find a Chrome solution yet.

    EDIT2: If it is truely stopping your connections (not just limiting it to 5 open connections, but if it is stopping all connections once you hit 5) then you probably want to find a way to keep your computer from requesting too many. You may be able to do something in Ubuntu IPTables or elsewhere to prevent Ubuntu from requesting too many connections across all applications. I do not know how to do this though, may be worth asking it in a different question.

  • Jason Robinson

    I had the same problem, ~25 tabs open usually and nothing loads when I fire up Chrome - they all just hang and then I refresh them one by one. Usually I can see around 350 sockets open after launching Chrome.

    I just managed to clear the problem by turning off "Predict network actions to improve page load performance" in Preferences -> Under the hood. All tabs load up nicely after closing and starting browser.

  • msw

    Does your machine have a private IP address? This would be an address of the form:

    • 10.x.x.x
    • 172.16-31.x.x
    • 192.168.x.x

    If so, you are connecting to the internet through a NAT box and it is getting overloaded or has limits on it to prevent overloading. This would be very unsurprising policy or accident in a university dormitory especially one where the "network shuts down from midnight to 7:00 am everyday". You may also be making a false correlation between your using Chrome and the failure; the kid down the hall may have set up a webserver or sumptin on the same day as you began using Chrome.

    Try another browser, and if that fails, learn to decode your sessions with wireshark to really see what is happening.