September 17th, 2008 at 11:11 pm

Well, solved for me anyway.  Sometime a few hours after it was released, Firefox stopped becoming my regular browser, and Chrome *did*.  I know — I was kind of amazed myself, in spite of all the plugins I’ve been missing.  At any rate, one thing I’ve begun noticing has been getting worse: its seeming inability to “resolve the host”.

This would lead to the browser essentially “hanging” and then timing out while it was waiting to fetch web pages.  For a browser that I’ve been relying on mostly … well, to browse … this was becoming problematic.

Turns out there are a few easy solutions for this that you can try:

1. delete your cache

2. delete your browsing history

3. delete your download history

4. disable “DNS pre-fetching”

Personally, I skipped right down to #4, and once DNS pre-fetching *was* disabled, Chrome was as zippy as ever.  As always use the above tips at your own risk if you feel like trying them out.  

via: Google Groups

One Response to “Chrome’s “Resolving Host” Problem Solved”

  1. jhay :

    Been having the same problem with Chrome lately so I also tried the same trick and it worked! Thanks :D

Leave a Reply.

Please note the comments policy

Sep
17
2008
11:11 pm