Chrome issues...

[blackroseMD1]

So, I'm experiencing some issues with the stable, beta and dev builds of Chrome.

First off, I was having issues with explorer.exe freezing. I though it was because I had added a custom start button into it, but then I noticed that whenever I closed Chrome, it would unfreeze.

Secondly, attached is what my task manager looks like when running Chrome. Now, I'm by no means an expert on browsers, but that seems to be a bit much.

Any ideas, or should I just dump Chrome and go back to FF?

 

[Capt.Jack Sparrow]

Hi Brian ,

You could try to run the Chrome in Single Process Mode

C:\Users\<User name>\AppData\Local\Google\Chrome\Application\chrome.exe" --single-process

See whether that makes a difference

Hope this helps

 

[richc46]

Member Jonathan_King will be all over me if he sees this, but I think that you should go back to FF. I know that you have the speed and all of that. But, it bothers me that Chrome is not compatible with some (although few) websites. Lets not get into a big discussion over this gang. Im just giving my opinion to the poster. I know many will disagree.

 

[blackroseMD1]

Member Jonathan_King will be all over me if he sees this, but I think that you should go back to FF. I know that you have the speed and all of that. But, it bothers me that Chrome is not compatible with some (although few) websites. Lets not get into a big discussion over this gang. Im just giving my opinion to the poster. I know many will disagree.

Rich,
Yeah, I used to be a huge FF fan, and the website incompatibility can be a PITA, but I love how useful some of the extensions on Chrome are. When I go back to using FF, I miss the accessibility that the extensions give me.

For some reason, the explorer.exe crashes seem to have stopped for now, and, while Chrome is still eating up memory, is just about the same as FF uses.

Jack,
Thanks for the info. I set the target shortcut with --single-process, and it's all running as one now. I happened to look that up, and found that you can also use --process-per-site so that if you have multiple tabs open on a single site, it will only run as one process.

 

[blackroseMD1]

Well, the explorer freeze is back. It's been present in every build of Chrome I've tried over the past two months. The only workaround that I have found is to start Firefox first, and then launch Chrome. For some reason, it doesn't freeze then.

It seems ridiculous that I have to launch another browser to keep Chrome from almost completely crashing my system and, after looking over at the Chrome help forums, it seems that I'm far from the only one with this issue.