Filed under: OS Updates, Windows Mobile

The Beta channel has been updated to 6.0.472.41 for Windows, Mac and Chrome Frame. It contains additional stability fixes, UI updates, and an updated set of translations. More details about additional changes are available in the svn revision log.

You can find out how to use the different Chrome channels at http://dev.chromium.org/getting-involved/dev-channel.

Google Chrome 5.0.375.127 has been released to the Stable Channel on Windows, Mac, and Linux.

Security fixes and rewards:
Please see the 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.
Aside from the listed security bugs fixed in Chromium, we have also deployed a workaround for a critical vulnerability where the root cause lies in an external component. Credit and $1337 to Marc Schoenefeld for enabling us to work around another Windows kernel bug [51070].

• [$1337] [45400] Critical Memory corruption with file dialog. Credit to Sergey Glazunov.
• [$500] [49596] High Memory corruption with SVGs. Credit to wushi of team509.
• [$500] [49628] High Bad cast with text editing. Credit to wushi of team509.
• [$1000] [49964] High Possible address bar spoofing with history bug. Credit to Mike Taylor.
• [$2000] [50515] [51835] High Memory corruption in MIME type handling. Credit to Sergey Glazunov.
• [$1337] [50553] Critical Crash on shutdown due to notifications bug. Credit to Sergey Glazunov.
• [51146] Medium Stop omnibox autosuggest if the user might be about to type a password. Credit to Robert Hansen.
• [$1000] [51654] High Memory corruption with Ruby support. Credit to kuzzcc.
• [$1000] [51670] High Memory corruption with Geolocation support. Credit to kuzzcc.

All

• [r55669] Fixed some minor issues with css custom cursor rendering (Issue: 51709)
• Re-enable the link to disable individual plug-ins in a group. (Issue: 51597)
• [r55596] Fixed playback rate for WebM/VP8 on certain content. (Issue: 51014)

Windows

• See All

Mac

• [r56026] Opening downloaded items from the download shelf now behaves as expected (Issues 32921,50263)

Linux

• See All

Known Issues

The Dev channel has been updated to 6.0.490.1 for Windows, Mac, Linux, and Chrome Frame platforms

All

• Late binding enabled for SSL sockets: High priority SSL requests are now always sent to the server first.
• Fixed focus problems with restoring from minimize (Issue 48917)
• Fixed Cannot add an address properly in the "AutoFill options" dialog box (Issue 50047)
• Several fixes and checks relating to syncing extensions (Issue 46516, Issue 49346, Issue 46516, Issue 49346, Issue 50567)
• Click-to-play is now behind the --enable-click-to-play command line switch.
• Fixed several issues with click-to-play (Issue 49686, Issue 49836)
  

Over at the Chromium blog, there's some good news for Chrome fans... Which is simultaneously bad news for those of you who already think they're getting a little silly with the version numbers. Starting now, Google plans to push a new stable version of Chrome every six weeks.

Yes, you read that correctly. Six weeks.

That's not set in stone, of course -- build issues and bugs could delay a release. Still, this means that the exciting new features you read about popping up in the developer channel will now likely have a shorter path to travel to the stable version. "We have new features coming out all the time and do not want users to have to wait months before they can use them," says the official blog post. It continues, "We basically wanted to operate more like trains leaving Grand Central Station (regularly scheduled and always on time), and less like taxis leaving the Bronx (ad hoc and unpredictable)."

Google also hopes the change will take some heat off the Chrome development team. Instead of having to rush to commit changes in the weeks and days leading up to a release, they'll be sliding in changes more frequently. If a feature isn't ready, they'll simply bump it to the next cycle.

It'll be interesting to see if this puts any heat on Mozilla, Opera, Microsoft, and Apple. Will they counter? Share your thoughts in the comments!

Oh yeah...Google also asks that you not pay too much attention to the numbers anymore as they stream past in the rear view mirror -- so no jokes, mmmkay?

The Dev channel has been updated to 6.0.466.0 for Windows and Linux

All

• Late binding enabled for SSL sockets:  High priority SSL requests are now always sent to the server first.
• The extension api “chrome.idle” has moved out of experimental and now has its own permission: “idle”.

Windows

• Fixed crash with SPNEGO authentication on intranet sites.

Linux

• Flickering favicons on Ubuntu Maverick should be fixed.  (There are other graphical glitches, but those also appear in other apps, so that appears to not be our bug.)
• Content settings window now uses a list instead of tabs.
• Remove unnecessary MIMEType field from application shortcuts.

More details about additional changes are available in the svn log of all revision.

The Dev channel has been updated to 6.0.458.1 for Windows, Mac and Linux platforms

All

• InfoBar should not be shown when the user first submits a form
. (Issue: 47426)
• AutoFill should continuously update profile data as the user submits forms with new data
AutoFill: Aggregate profile data. Remove the AutoFill InfoBar. Remove more remnants of shipping address and CVV. (Issue: 47423)
• When editing a field in a previously auto-filled form, only display unique suggestions
AutoFill: Remove duplicate suggestions when providing suggestions for a field (Issue: 47436)
• Enabling sync freezes Chromium
Remove NIGORI from the sync routing info. (Issue: 47766)

Windows

• Chrome unable to start if other FFmpeg DLLs are present on the system (Issue: 35857)