Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

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

For some reason Google Chrome is slow when I'm working against localhost. I had the same problem in Firefox 3.5 but I changed some IPv6 setting in about:config which fixed the issue. I think the same problem occurs in Google Chrome, but I can't find out how to fix it.

Any ideas?

share|improve this question

migrated from Sep 19 '09 at 16:15

This question came from our site for professional and enthusiast programmers.

up vote 23 down vote accepted

Just an idea : do you have a line that looks like this :

::1 localhost

in your hosts (it should be somewhere like C:\WINDOWS\system32\drivers\etc\hosts, if I remember correctly) file ?

If yes, comment that line by adding a # at the beginning.

This way, the only line that's about localhost should be    localhost

which is IPv4.

It might help, if your problem is really caused by IPv6.

share|improve this answer
Thanks a million! – blahblah Sep 19 '09 at 15:55
You're welcome :-) Was just a wild guess, but nice to seen it worked ! (might be useful one day on another, actually ! ) – Pascal MARTIN Sep 19 '09 at 15:56
This makes a huge difference. Both lines were commented out for me in Windows 7, so I uncommented the IPv4 line and everything works great now. – Ben Mills Feb 1 '10 at 16:27
I've been using this fix up until Chrome 8, but now that Chrome 9 has been released, it seems to be slow again. Has anyone found a fix for the current version? – Douglas Feb 21 '11 at 10:45
Can someone explain why does this work? – Pacerier Jul 16 '12 at 17:01

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .