Anyone having problems with Chrome 21.0.1180.60?

I had to downgrade to an earlier version because 21.0.1180.60 was freezing about a 1/4 of the time during browser startup. I am running XP Pro SP 3 with Avast 7 Pro.

Back on 20.0.1132.57 and all is well again.

Never had anything like this before with Chrome. Weird!!

 

Probably the PPAPI Flash.

 

And here i thought it was my machine..

Thanks for that..

 

Not a single issue here on Win 7 Ultimate SP1 x32 after update.

 

Yes.
I started this thread on the matter.
A fellow member (credit to Scoobs72!) suggested that I exclude the Chrome application folder in my firewall (Online Armor).
His suggestion worked perfectly.
You could try the same thing with avast! Pro. Might work.

 

The only oddity I experienced when updating Chrome in a relative's system was that, after reopening it, the extensions were gone. I had to reinstall them.

 

I just discovered another problem. It was really driving me crazy, spending a lot of time trying to figure it out. Long story short, the Brother printer connected to my W7 machine began misbehaving dramatically. One of the things it was doing was popping up 2 'Manual Duplex Instruction' dialog boxes when I clicked Wrench\Print in Chrome. These are for when a user wants to print on both sides of a page, which is not what I was trying to do at all. I struggled with this for several days until I finally noticed that the 21.0.1180.60 update had placed a checkmark in the Options panel next to 'Two-sided'... something I had never even noticed existed before. My printing problems and the Brother dialogs disappeared as soon as I removed the checkmark from this Option. I note that this was only happening on a W7 machine. Another computer on the network (running XP and using a different Brother printer) has not been affected in this manner, and the Chrome print panel does not have the 'Two-sided' Option checked. Weird.
Edit in: I actually have to keep removing the checkmark from this box each time I go to print in order for it to not mess up.

 

Looks like they've addressed this issue in the current beta...