Google’s Chrome: One Retraction, Two Things It Does Wrong
by Tony Hung on September 9, 2008
So I’ve been using Chrome for a little while. I still likes it, but there are a few things that have come to my attention that require me updating my original post. One retraction of sorts, and two other things that greatly annoy (and maybe its just me).
1. Chrome isn’t as “small” as I thought: I cottoned on to this fairly quickly after my initial post. Chrome isn’t kidding when it talks about thinking of each tab as its own set of processes; if you have a look at the Windows Task Manager, you’ll find there are many many instances of Chrome floating around, probably in some way representing all of the separate silo’d processes that Chrome is touting. Yes, this is probably good for stability. But I was initially bufalloed into thinking that Chrome only took up, say, 40-60mb of memory, when in fact, that was only a single “process” I was picking up. On heavier days, Chrome uses easily as much as Firefox, that is, in excess of 100 mb of RAM, and possibly almost 150 mb.
2. Chrome has problems resolving URLs: I’m not sure what it is, but for some reason I’ve noticed that Chrome has a problem with resolving URLs. You know: websites. Its inconsistent with the kinds of websites, but some of them are big and some small. It drives me nuts, because there’s no particular rhyme or reason to it.
3. Chrome shows your most visited websites — and you can’t change that (for now): When you open up a new tab, Chrome “helpfully” shows your most visited URL’s via your web history. If you have not decided to be discrete via the “incognito” function, you might find some surprising URLs that show up that you might not want others to see. Case in point: I was looking for a gift for my wife the other day. POOF — URL shows up when she decides to try Chrome the other day. In this “SFW” example, I was busted and embarassed. But in this iteration of Chrome this is something you cannot change, alter, or delete single sites, and instead have to delete your entire browsing history.

6 comments
Huh, I haven’t heard of issue #2 at all from other people. Are there any sites that reliably have problems resolving? Are you using anything unusual like OpenDNS or other things? Mind if I ask which ISP you’re using?
by Matt Cutts on September 9, 2008 at 11:06 pm. #
I agree, have had no problems with URIs in the past seven days of using Google Chrome.
This are early bugs and would be fixed in the upcoming releases of Chrome, thus making it better.
What I’m really waiting for are the plugins and extensions the community will come up with.
by jhay on September 9, 2008 at 11:52 pm. #
Was it a gift for your wife or more realistically some porn website ?
;-)
by Da Bourz on September 10, 2008 at 2:16 am. #
Don’t get me wrong, I love Chrome so far, and would probably use it a lot more had it been available for Mac OS X as well. However, Tony, there are options. Have you tried Safari for Windows? On Mac at least it boots up instantly and is a fast experience, and also more widely supported than Chrome. Granted, not much bling, but it gets the job done.
Another solution would of course be to buy a new computer. If Firefox takes 90 seconds to start, it is probably way overdue…
by tdhedengren on September 10, 2008 at 4:25 am. #
The two things that have annoyed me the most – one bug and one feature:
#1 bug – I find on Vista if you run chrome @ max and have your windows taskbar auto-hiding you can’t get to it. (i.e. going to the bottom of the screen doesn’t pop-up the taskbar). Not the end of the world but the only way to get your taskbar to pop-up is to un-maximize EVERY window (not just chrome) but it only happens when chrome is maxed.
#2 feature – no spellchecker. this feature alone is why I use FF above any others. inline spellchecking in any text window is so darn handy. I’m also used to it now so I find with Chrome I’m missing typos because I expect the redline to pop-up
by Ryan Coleman on September 10, 2008 at 9:50 am. #
[...] 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 [...]
by Deep Jive Interests » Chrome’s “Resolving Host” Problem Solved on September 17, 2008 at 11:11 pm. #