Google Chrome Stalls Again

You know, I wasn’t sure what I would blog about today, but Google made my mind up for me. I’m using my IE browser to write this blog post because Google Chrome once again, stalled for no reason.

What do I mean by stalling? I type web addresses into the address bar and hit enter . . . and wait . . . and wait . . . nothing. I can’t even go to Google.

This happens a couple of times per day. I thought it was some kind of cache problem because it usually happens after I’ve had it open all day while working. But this morning it happened on about the third time I tried to use it.

Google says they can handle running DNS for millions of people through their Google DNS initiative. If they can’t serve up their own browser consistently, there is no way ICANN should work with them to run people’s DNS.

What does one have to do with the other? It comes down to server abilities. Google Chrome has no way for you to set your own cache limits. I assume that is because they are preset and the Google Chrome Browser depends on their servers to carry the load.

I may have it totally wrong. If I am, I hope there are some programmers or IT people that can tell me why Google Chrome stalls the way it does.

Ok, a search found this thread. It says to do the following;

 If you run the latest dev build with the command line –new-safe-browsing, the issue should be resolved. To do so, follow these steps:

You can add the command line flag to shortcut used to launch Google Chrome by:

1. Right click the Google Chrome icon on the Windows Quick Launch bar or desktop shortcut

2. Select “Properties”

3. Choose the “Shortcut” tab

4. Add –new-safe-browsing to the “Target” field after chrome.exe

5. Click OK

6. Restart Google Chrome from the shortcut you just modified

7. Make sure that “Enable phishing and malware protection” is checked (wrench menu –> “Options” –> “Under the hood”)