Google Chrome caused problems with Firefox & Safari

[DaviDC.]

I was enjoying using Chrome. Most of the features were working & it was fast but there were times I wanted to use Firefox. The problem was that Firefox was acting strangely with way to many spinning beachballs, which had never happened before. Several times it was completely unresponsive & even doing a Force Quit took a long time to accomplish.

This morning I tried to find out what the problem was. Firefox was useless & even Safari wouldn't launch so I got rid of Google Chrome, restarted the computer, & all seems to be back to normal.

It looks like the folks at Google expect Chrome to be the only browser on a computer. Or at least the only browser that will work. I don't think that's the way to win fans of an application.

[Zoidberg]

Installed the developer version here too; I don't have Firefox but I've not noticed any problems with Safari.

[MacManMaz]

After diving in and setting up a Google Work group and website for our Union at work, I've come to the conclusion that most of Google's Applications are "half baked" and they don't do the walk as far as the talk leads you.

Lots of features that have bugs, or just don't work as advertised.

[silvarios]

Wait, did you not try to restart your computer before you trashed Chrome? Perhaps it was the restart the cured the problem.


Nathan

[DaviDC.]

silvarios wrote:
Wait, did you not try to restart your computer before you trashed Chrome? Perhaps it was the restart the cured the problem.


Nathan

I restart my computer far more often than many people here seem to do. Whenever anything starts behaving strangely, I restart, then usually repair permissions.

Chrome might be a fine browser one day, but that day hasn't arrived for Mac users yet.

[silvarios]

Of course not, Chrome is but a developer preview. I don't have it installed on any of my Macs for that very reason. My question, how does having Chrome installed and not running effect any other browser on your Mac?

Oh and I don't think Repairing Permissions does what you think it does. Repairing permissions doesn't generally do anything on non Apple apps.