Entries RSS · One reason I don’t like Google Chrome on the Mac
In my continuous drive to “pimp” my Mac experience, I use this application switcher called “LiteSwitch.” It hasn’t been updated in years, but it still works and amongst some other cool features, it allows me to see (and manipulate) all running processes, including the hidden ones (which I choose to hide on a case-by-case basis).
Here’s what the Google Chrome Browser shows me.
Every time I open multiple tabs, it shows me a process, called Google Chrome Helper. With half a dozen tabs open, I soon have these processes filling up my whole tab-switcher.
I realise that Chrome is in alpha, beta, or whatever disclaimer they use these days, but I just think it’s really messy. Ironically, it is the fastest browser on my system and I really do lean towards it when quickly wanting to browse the net. Even though the average user will not see these aesthetic little bugs, I sincerely hope that they clean it up a.s.a.p.. Even Chromium, its seemingly more mature brother, displays the same behaviour.
Stop being so beta, Google!
/Vincent
Like
Related posts:
Some has fluffed a plist parameter in the app bundle, theirs an Boolean switch which lets you hide child processes.
I don't know enough to fix but I think there should be some documentation over at Apple on how to Fix this.
just did a google search and couldn't find it. If I do, I'll update my post with it.
I don't understand your concern. According to what I've understood, it makes the browser able to keep working even if one of the tabs has a problem. Therefore it's somehow better for the whole system, as an unworking tab doesn't prevent the user to keep working with the other tabs. Am I right ?
But that`s how Chrome works! That`s the whole idea behind it! Chrome launches a separate process for each tab and as a result, each tab has it`s own memory allocated and its own processor time gap so all the hyperRich websites do not interfere. And if any of them enters infinite loop or anything you always can shut the tab, without the need to close the browser or without it freezing altogether. it addresses a memory leak issues too.
Don`t you read the overviews and descriptions of things you install?
The problem of those processes showing up improperly is rather the OS/setup issue, than Chrome`s, I think.
Yep, this is a feature of Chrome and completely intentional. Google has obviously gone out of their way to hide the separate processes from the regular Mac OS X application switcher, and it's not their fault LiteSwitch does crazy stupid voodoo to show these hidden processes.
I would say you should wait for LiteSwitch to be updated, but since it's basically obsolete (its whole purpose was to make a HUD-like app switcher, back when OS X didn't have one. Now OS X has one itself) I don't imagine that's going to happen. Maybe time to either give up Chrome or give up LiteSwitch.
I know what you mean,
I’ve never seen my cpu so hot (190ºF and fans spinning over 3000rpm!! I’m usually between 110º-140º and that’s crazy hot as it is). Is Chrome trying to fry our laptop? I’m surprised I haven’t damaged my internals or lap but it smells like new plastic in here! Yikes, I better only open one or two tabs from now on. Thanx for the Chrome Beta limitation tip!