In order to fix the problem with the Google Chrome Browser, I found in several of the Google Discussion Forums about this problem the recommendation to do a "System Restore". This is of course a quite brutal way of fixing a problem; better would be if there was a clear guidance on what settings specifically would need to be changed in order to remove that obnoxious behavior of Google Chrome not to find web sites at the first try.
But I now did a System Restore, beyond the date of when I noticed this behavior occurring more frequently. And - it seems to have cured the problem: Chrome now finds all the site immediately, waits properly until all various sites / images / iframes within a site have been loaded properly, and does not spit out that error message about not finding a site anymore.
The System Restore is supposed to let files and documents untouched, that is any new files since the restore point would still be there. However, when I looked at one of my folders, there were all those new files missing. I did then a search for one particular file which I knew had been in this folder, and in the search the file showed up - in exactly that folder! When I then looked again at this particular folder, it now had all the files in it that appeared to be missing at the first glance. So what must have happened: after the system restore the folder view appeared to have some kind of "image" or "status shot" in memory, a kind of cached version of the folder view as it was at the time of the system restore point to which I had reverted. However, only after again viewing it, the content view was actually updated. So everyone who is making a system restore needs to be aware of this: the views of the folders need to be refreshed, to see the latest true content and not the "imagined" content at the time of the system restore point.
Showing posts with label Google Chrome. Show all posts
Showing posts with label Google Chrome. Show all posts
Sunday, March 14, 2010
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 4.0.249.89.
When trying Firefox or Internet Explorer, these problems do not occur at all. So I attribute it to something inherent to Chrome.
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 4.0.249.89.
When trying Firefox or Internet Explorer, these problems do not occur at all. So I attribute it to something inherent to Chrome.
Monday, March 01, 2010
Problems with Google Chrome
Since Google Chrome came out, I have been using it as my main browser. I like its clean interface which to me is a bit more appealing than FireFox, and its fast loading which beats Microsoft's IE 8. Quite strange that in a recent survey it came out that in the UK the Google Chrome browser only has a share of 5%. But there may be reasons for this, as I too have some issues with this browser which have yet prevented me from making it my default browser: I still have MS IE 8 and Firefox on my computers, just in case something does not appear right. And one thing seems to be the handling of JavaScript.
One example: When I checked on Spiegel Online the Medal Statistics of the 2010 Vancouver Winter Olympics, the table appeared to be faulty in Google Chrome: instead of country names there was only "undefined", and the flags were empty rectangles. When looking at the same page in MS IE8, everything was shown correctly. What could be the reason for this? I have no idea... Gears is installed properly, the browser version is 4.0.249.89, up-to-date. Unfortunately the user interface sleekness of Google Chrome has the disadvantage that there are no settings for me to control: I did not find anywhere to "enable Javascript" or something similar...
Another strange thing: I wrote some HTML code for a few web pages with images, and I used the "alt" attribute there, to give an alternative textual description of the image. In all browsers this "alt" attribute is shown when hovering with the mouse over the image, like a tooltip. Not so in Google Chrome: nothing appears. This may be actually closer to the intended web standard use, which recommends to employ the "title" attribute for tooltip-like information... I may have to change my web pages to properly take care of this.
One example: When I checked on Spiegel Online the Medal Statistics of the 2010 Vancouver Winter Olympics, the table appeared to be faulty in Google Chrome: instead of country names there was only "undefined", and the flags were empty rectangles. When looking at the same page in MS IE8, everything was shown correctly. What could be the reason for this? I have no idea... Gears is installed properly, the browser version is 4.0.249.89, up-to-date. Unfortunately the user interface sleekness of Google Chrome has the disadvantage that there are no settings for me to control: I did not find anywhere to "enable Javascript" or something similar...
Another strange thing: I wrote some HTML code for a few web pages with images, and I used the "alt" attribute there, to give an alternative textual description of the image. In all browsers this "alt" attribute is shown when hovering with the mouse over the image, like a tooltip. Not so in Google Chrome: nothing appears. This may be actually closer to the intended web standard use, which recommends to employ the "title" attribute for tooltip-like information... I may have to change my web pages to properly take care of this.
Subscribe to:
Posts (Atom)