Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm using Chrome (Version 22.0.1229.94). About 20% of pages simply stop loading after a second or two. Sometimes, I'm able to click an early link after a second or third reload. If I attempt to close the page, it continues to hang for a few (10-30) additional seconds, then closes. However, if I switch to other tabs, it works just fine. If I don't change tabs and wait long enough, it says that there's something on the page that's taking too long to run and offers to let me kill it.

Only a select number of sites fail to load, and they do so consistently. None of the stackexchange sites or google fail, but others like realclearpolitics and wowwiki do. I visit those sites every day, and this is the first time it has failed like this.

If it were just one site, I would say someone messed something up in their deployment. But it seems incredibly peculiar that suddenly, half a dozen popular sites all mysteriously have the same symptoms.

If I attempt to load the pages in Firefox or IE9, they load just fine.

Nothing new has been installed, regarding Chrome or otherwise. Antivirus reports no abnormalities. System is regularly patched. Restarting both chrome and the computer have had no effect.

share|improve this question
What about your DNS settings? – user3463 Oct 25 '12 at 22:35
If it were a DNS issue I wouldn't be able to get just about anywhere. Specifically, the site wouldn't start loading and then just fail. – corsiKa Oct 25 '12 at 22:43
And when you changed your DNS settings as part of your test, did you notice any difference in the behaviour of Chrome? – user3463 Oct 25 '12 at 22:52
You can't possibly be serious, but sure I'll humor you. As part of my test, I used a separate browser (note the second to last paragraph) and no problems were noted. This rules out problems with the connection itself, of which DNS is a subset, unless somehow Chrome has some magic override to DNS settings or other connection settings, which I find incredibly unlikely. – corsiKa Oct 26 '12 at 16:11
Chrome's cache is legendary for storing things like DNS along with the HTTP cache. Have you tried clearing it out completely? I've learnt to assume nothing when it comes to Chrome. There's a lot of "magic" happening under the hood that is different to other browsers. – user3463 Oct 26 '12 at 19:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.