The Chrome team is excited to announce the release of Chrome 21 to the Stable Channel. 21.0.1180.57 for Mac and Linux. 21.0.1180.60 for Windows and Chrome Frame. Chrome 21 contains a number of new features including a new API for high-quality video and audio communication. More detailed updates are available on the Chrome Blog.

Security fixes and rewards:Please seethe Chromium security page for more detail. Note that the referenced bugs may be kept private until a majority of our users are up to date with the fix.

Many of the above bugs were detected usingAddressSanitizer.We’d also like to thank Drew Yao / Braden Thomas / Jim Smith (all Apple Product Security), Kostya Serebryany of the Chromium development community, Atte Kettunen of OUSPG and Bernhard Bauer of the Chromium development community for working with us during the development cycle and preventing security regressions from ever reaching the stable channel.

Full details about what changes are in this release are available in the SVN revision log. Interested in hopping on the stable channel? Find out how. If you find a new issue, please let us know by filing a bug.Karen GrunbergGoogle Chrome

So I'm using Pepper Flash now, which is actually working decently compared to every previous time I've tried it, but HD video playback quality seems to have decreased somewhat? It seems a bit more pixelated.

It seems as if the "insecure content" warning that used to be given when an https page loads http assets has been removed. Chrome now seems to block such assets unconditionally. This has serious consequences for us. Can you guys please comment? Is there a way for the user to allow such assets on the page?

@M. A. Sridhar: thanks for commenting. I'm just writing a blog post about Chrome's new mixed script blocking. Due to user confusion, the mixed script warning is now more subtle -- but it still exists. Look for the shield in the omnibox.

As a reminder, mixed scripting can be a serious security condition so should be fixed ASAP.

simone im glad im not alone on this :Dgo type about:plugins in the serch bar and disable and you see shockwave flash click on the plus and then disable this:Shockwave Flash 11.3 r31 for me its the first one close and openhave a good day bro :D

simone and others with the flash audio problem, please come to http://code.google.com/p/chromium/issues/detail?id=139953 and leave us information on your configuration. We are working hard to resolve the issues as quickly as possible. Thank you!

jor@i got some answers in google forums it pepper flash related issue disabling it fixes it even if i enable hardware acceleration if not fix all issue glad my tip help some of you i feel good about myself now XDcheers :D

Not only are the favicons now stupid looking blank pages in the Omnibox, but the Bookmarks Bar no longer has the saved link's icon in the address bar. Now THAT looks really stupid! Someone at Chrome failed to think through doing away with the favicons in the Omnibox, because I cannot believe they want Chrome users (that use the Bookmarks Bar) to have blank pages as the saved link icons. You need to re-think this change!!!

This is the absolute worse update ever. Way too many issues since the last update. I've loved using Chrome, but this is stupid crazy. I'm going to use another browser until this is (hopefully) all worked out - then, maybe I'll be back.

Flash videos installed locally on a computer no longer work unless PepperFlash is disabled. The videos consist of training videos installed on a customer's computer. The videos are viewed using the default web browser - if the user has Chrome with the newest version, the browser opens only a black window and the video will not play. The only workaround is disabling PepperFlash - but the average user will not know how to do this. It appears the viable option is to have our customers user a none-Chrome browser.

Can you guys stop messing with the GUI and start actually working on the performance issues? This issue with S&P-Flash is getting too far, people hating the new "look" this isn't a real 'stable' channel to me.

I don't want to start kicking chrome in the backside for it, I get fixes can't come just by request and are only fixed when it's possible to be done.. but come on.

First and Foremost;

CAN I BE THE ONE IN CONTROL OF MY 'FAVORITE PAGE' THUMBNAILS PLEASE... But performance issues first!

Not sure if it's just me or not but the WikiBooks website isn't showing at all in Chrome. Works fine in other browsers. The source of the page is all downloaded, but Chrome only shows a blank white page https://secure.wikimedia.org/wikibooks/en/wiki/Main_Page

@Chromana did you try to click on the shield in the omnibar and then enable unsafe content?

Anyway guys, I didn't like this release, I have to admit it, but come on don't be so evil I'm sure the Chrome Team is working on it hard. Developing isn't that easy, you should know it.Don't forget to use the bug report.

The PepperFlash plugin causes my Windows 7 system to instantly reboot with a solid black or white screen when playing Flash videos. Disabling and using the standard plugin works fine. Took me hours to figure this out. Nice 'stable' release.

YouTube audio and video are out of sync with this update. Other Flash players, like BBC iPlayer, seem to be fine.

@Simone thanks a lot, that's what it was. They should really make it more obvious in Chrome when they hide stuff. I'm very good with computers and I missed it, not sure how non-technical people would cope!

GOOGLE TEAM...I wanted to say this but Chrome has been having big bugs for the last 7 months. Like when I try to go to Wikipedia it shows nothing and sometimes when I go on Facebook it says something about the site being suspicious the page with the red background. The worst of all everyday Chrome is randomly making the computer unstable and crashes it. If you can compare the chrome from December 2011 to today's chrome some of these bugs wouldn't exist. It was super stable compare to the last 7 months.

I strongly suspect the tech reporters will have a field day with this latest update - suggesting that Chrome may not be as good as people having been saying it is. Seems they are probably right...

Karen - the longer you delay fixes, the worse Chrome's reputation will become. I don't care if you have ten updates in a single day - ADDRESS THE PROBLEMS right away and get them corrected and behind you. Every hour that nothing is done is an hour too long. Damage has already been done...and waiting to correct the problems just makes Chrome look very, very bad.

Chrome - you blew it by creating problems...and you blew it again by not addressing the problems immediately, even if it meant reverting to older yet stable and sound channels.