Fixing Chrome

When it comes to web browsers, I prefer Chrome (general purpose), Firefox (when I’m exploring new areas – it’s better protected), and Internet Exploder… well, if you must.

I use Chrome for instance write now, updating the blog.

But for the past several days, Chrome has been acting up. Every time I’d launch it all the desktop icons would blink, go blank, then recreate themselves. It only happened launching Chrome, and nothing else has changed.

A bit of searching showed others were beset with the same problem… and the answers ranged from the Microsoft garbage of “re-install Windows” (emphatically NO!), to clearing the icon cache, to restarting Windows, to just accepting it and waiting for a fix, to checking an obscure item in the chrome://flags list.

Hmm… now we’re getting somewhere.

The pseudo-URL chrome://flags exists to control various experimental ‘features’ in Chrome. One especially buggy item is Chrome’s “profile manager” which showed up on the most recent release. Profile Mangler attempts to keep track of who is using the browser… useful in a shared-machine environment but not something I care about. If you have it enabled it will show up on the top bar of Chrome, just to the left of the control group, with the current user’s name in a small box.

If you’re having the issue, you have two choices. The first (safest) choice is to live with the bug and wait for Chrome v41 to appear. They’ve found the bug, repaired it and merged it into 41.

The second choice: open another instance of Chrome. Browse to the pseudo-URL chrome://flags. Find the key “Enable new profile management system” and set it to “Disabled”. Also find “Enable the new avatar menu” and set that to “Disabled.”

Restart Chrome and the problem will go away.

…and make a note that you did this so you can go and reverse it back when the new version comes in a few weeks.

Advertisements

2 thoughts on “Fixing Chrome”

  1. So far I have not heard of anybody else having this issue however I have seen my share of Chrome issues in the past! Thanks for the post, I need to start doing the same on my blog. =)

  2. I think it’s mostly an issue for users running multiple Google accounts – especially Google Apps admins. The fix is merged into v.41 which should go ‘stable’ in the next week… at which point this bug, at least, will be history.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s