Thursday, March 11, 2010

Trouble with Google Chrome Browser

This time of the year seems to be the time where everything appears to go wrong somehow. In recent weeks I have experienced significant trouble with the Google Chrome Browser: when I try to access a page, often the message comes:

This web page is not available.

The web page at null might be temporarily down or it may have moved permanently to a new web address.

This indicates actually two bugs: the null should show instead the base URL, and overall the page should load because it is available. This message shows up very shortly after I try to access the page, so it seems that some timeout has been set incorrectly. Hitting reload a few times eventually loads the page, but this is very unsettling, especially when making a payment on the web: it happened several times that during the pay process I had to reload the pages - hope I will not get multiple payments. This problem happened since about 2 weeks; I first had attributed it to a slow and faulty connection, but when I dug a bit deeper and searched for this issue on the web, I came across a lot of posts who complained about the same thing in the Chrome browser. The null-issue is described at the Chromium project as a bug that they are aware of - it obviously only appears in the UK-English area. The other bug is harder to fix. I managed to set a new DNSQueryTimeout in the registry - now the problem only appears when accessing a page with https. The Chrome version I use is

When trying Firefox or Internet Explorer, these problems do not occur at all. So I attribute it to something inherent to Chrome.

No comments: