Comments on: Problems with Google Chrome? Try This http://www.xxeo.com/archives/2008/10/27/problems-with-google-chrome-try-this.html 20 minutes into the future... Wed, 10 Feb 2010 21:19:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Jim Roskind http://www.xxeo.com/archives/2008/10/27/problems-with-google-chrome-try-this.html/comment-page-1#comment-109953 Jim Roskind Wed, 29 Oct 2008 00:34:30 +0000 http://www.xxeo.com/archives/2008/10/27/problems-with-google-chrome-try-this.html#comment-109953 <p>Thanks for reporting this issue. I tried to transcribe it into a bug on chromium.org, and perhaps you can add some additional details.</p> <p>Please visit:</p> <p>http://code.google.com/p/chromium/issues/detail?id=3819</p> <p>Thanks for using Google Chrome, and thanks in advance for submitting any more details which might help us resolve such a problem.</p> <p>As I tried to note in the bug report, there are two caches, one in the application, and one in the OS (which you were able to flush). I suspect that the additional problems you saw after doing a "ipconfig /flushdns" were a result of the application cache. You can flush that cash by exiting and restarting Google Chrome (note that Google Chrome can be configured to re-open all your original tabs on restart, if you chose to experiment with it.)</p> <p>You may also be able to get some data from examining either "about:dns" (which reports stats on your DNS resolutions, or by looking at "about:histograms/DNS" which provides more details, without describing specific host names.</p> <p>I'm most concerned about how/why you are getting bogus "name not found" resolutions from your network. IF you feel up to the task, you might try using something like Wireshark to confirm that your system is indeed getting such negative resolutions.</p> <p>One other thing that suddenly dawned on me... perhaps you might also add to the bug report any anti-virus or firewall software that you are using, as that may also play a role.</p> <p>Thanks again for your help,</p> <p>Jim</p> <p>Opinions expressed are mine, and not my employers.</p> Thanks for reporting this issue. I tried to transcribe it into a bug on chromium.org, and perhaps you can add some additional details.

Please visit:

http://code.google.com/p/chromium/issues/detail?id=3819

Thanks for using Google Chrome, and thanks in advance for submitting any more details which might help us resolve such a problem.

As I tried to note in the bug report, there are two caches, one in the application, and one in the OS (which you were able to flush). I suspect that the additional problems you saw after doing a “ipconfig /flushdns” were a result of the application cache. You can flush that cash by exiting and restarting Google Chrome (note that Google Chrome can be configured to re-open all your original tabs on restart, if you chose to experiment with it.)

You may also be able to get some data from examining either “about:dns” (which reports stats on your DNS resolutions, or by looking at “about:histograms/DNS” which provides more details, without describing specific host names.

I’m most concerned about how/why you are getting bogus “name not found” resolutions from your network. IF you feel up to the task, you might try using something like Wireshark to confirm that your system is indeed getting such negative resolutions.

One other thing that suddenly dawned on me… perhaps you might also add to the bug report any anti-virus or firewall software that you are using, as that may also play a role.

Thanks again for your help,

Jim

Opinions expressed are mine, and not my employers.

]]>