release
Stable and Beta Channel Updates
- Updated UI
- Form Autofill
- Syncing of extensions and Autofill data
- Increased speed and stability
More information on these and other changes in Chrome 6 can be found on the Google Chrome blog. Download Chrome today!
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.
- [34414] Low Pop-up blocker bypass with blank frame target. Credit to Google Chrome Security Team (Inferno) and “ironfist99”.
- [37201] Medium URL bar visual spoofing with homographic sequences. Credit to Chris Weber of Casaba Security.
- [41654] Medium Apply more restrictions on setting clipboard content. Credit to Brook Novak.
- [45659] High Stale pointer with SVG filters. Credit to Tavis Ormandy of the Google Security Team.
- [45876] Medium Possible installed extension enumeration. Credit to Lostmon.
- [46750] [51846] Low Browser NULL crash with WebSockets. Credit to Google Chrome Security Team (SkyLined), Google Chrome Security Team (Justin Schuh) and Keith Campbell.
- [$1000] [50386] High Use-after-free in Notifications presenter. Credit to Sergey Glazunov.
- [50839] High Notification permissions memory corruption. Credit to Michal Zalewski of the Google Security Team and Google Chrome Security Team (SkyLined).
- [$1337] [51630] [51739] High Integer errors in WebSockets. Credit to Keith Campbell and Google Chrome Security Team (Cris Neckar).
- [$500] [51653] High Memory corruption with counter nodes. Credit to kuzzcc.
- [51727] Low Avoid storing excessive autocomplete entries. Credit to Google Chrome Security Team (Inferno).
- [52443] High Stale pointer in focus handling. Credit to VUPEN Vulnerability Research Team (VUPEN-SR-2010-249).
- [$1000] [52682] High Sandbox parameter deserialization error. Credit to Ashutosh Mehra and Vineet Batra of the Adobe Reader Sandbox Team.
- [$500] [53001] Medium Cross-origin image theft. Credit to Isaac Dawson.
This release also fixes [51070] (Windows kernel bug workaround; credit to Marc Schoenefeld), which was incorrectly declared fixed in version 5.0.375.127.
In addition, we would like to credit Google Chrome Security Team (Inferno), James Robinson (Chromium development community), Google Chrome Security Team (Cris Neckar), Aki Helin of OUSPG, Fred Akalin (Chromium development community), Anna Popivanova, “myusualnickname”, Michal Zalewski of the Google Security Team, kuzzcc and Aaron Boodman (Chromium development community) for finding bugs during the development cycle such that they never reached a stable build.
Windows Phone 7 goes RTM
Filed under: OS Updates, Windows Mobile
Beta Channel Update
Dev Channel Update
The Beta channel has been updated to 6.0.472.41 for Windows, Mac and Chrome Frame
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
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.
The Dev channel has been updated to 6.0.495.0 for all platforms
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 Beta channel has been updated to 6.0.472.36 for all platforms
All
- More UI Polish
- Stability Fixes
- [r55562] Re-enable the link to disable individual plug-ins in a group. (Issue: 51597)
Mac
- [r55585] Insert the Update Chrome item to existing Wrench menus when notified. (Issue: 50659)
Chrome Frame
- [r55941] Fix Chrome Frame upgrade from old to new beta. (Issue: 51620)
More details about additional changes are available in the svn log.
You can find out about getting on the Dev channel at http://dev.chromium.org/getting-involved/dev-channel.
If you find new issues, please let us know by filing a bug at http://crbug.com/new.
Jason Kersey
Dev Channel Update
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)
Google Chrome 6.0.472.33 has been released to the Beta Channel for all platforms
Updates from the previous beta include:
- Updated UI
- Form Autofill
- Syncing of extensions and Autofill data
- Increased speed and stability
These changes and more in Chrome 6 Beta are explained in more detail on the Google Chrome Blog.
To switch to the Beta channel, you can download Google Chrome
Google Chrome 5.0.375.126 has been released to the Stable channel on Linux, Mac, and Windows
The Chrome Dev Channel has been updated to 6.0.472.25 for all platforms
- UI Updates
- Stability Fixes
- (Issue 50577) Launching Chrome after installing may not work correctly if other browsers are running and set as default
- (Issue 51187) Drag and Drop of large file may result in crash
- (Issue 51325) Home button on Linux has no image
The Chrome Dev Channel has been updated to 6.0.472.22 for all platforms
All Platforms
- UI Updates
- Stability Fixes
- (Issue 50577) Launching Chrome after installing may not work correctly if other browsers are running and set as default
- (Issue 51187) Drag and Drop of large file may result in crash
Dev Channel Update
All
- UI tweaks and clean up
- Additional stability fixes
Linux
- PDF Plugin does not load - Issue 49702Mac
- PDF plugin does not load - Issue 49800
You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel.
If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry.
The Dev channel has been updated to 6.0.472.11 for all platforms
This release contains
- UI tweaks and clean up
- Additional stability fixes
Known Issues
- PDF plugin does not load on Linux (Issue 49702) and Mac (Issue 49800)
More details about additional changes are available in the svn log of all revisions
You can find out about getting on the Dev channel here: http://dev.chromium.org/getting-involved/dev-channel
If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry
Jason Kersey
Google Chrome
Google Chrome 5.0.375.125 has been released to the Stable channel on Linux, Mac, Windows, and Chrome Frame
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 workarounds for two critical vulnerabilities where the root cause lies in external components. Credit and $1337 to Marc Schoenefeld for enabling us to work around a Windows kernel bug [48283]. Credit and $1337 to Simon Berry-Byrne for enabling us to work around a glibc bug [48733].
- [$500] [42736] Medium Memory contents disclosure in layout code. Credit to Michail Nikolaev.
- [$500] [43813] High Issue with large canvases. Credit to sp3x of SecurityReason.com.
- [$500] [47866] High Memory corruption in rendering code. Credit to Jose A. Vazquez.
- [$500] [48284] High Memory corruption in SVG handling. Credit to Aki Helin of OUSPG.
- [48597] Low Avoid hostname truncation and incorrect eliding. Credit to Google Chrome Security Team (Inferno).
If you find issues, please let us know: http://code.google.com/p/chromium/issues/entry
Google cranks up the speed on Google Chrome release cycle
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?
Dev Channel Update
All
- [r52790] Chromium stops saving files for any large downloads (Issue 49216)
- [r52693] Fix crash with SSL client auth (Issue 49197)
- [r52850] Option clicking a link now saves a resource directly without triggering a “Save As...” dialog (Issue 36775)
Mac
- [r52911] Implement the upgrade available notification on the Wrench menu (Issue 45147)
- [r52485] Implement the new, unified Wrench menu (Issue 47848)
Linux
- [r52507] Fixed tab dragging glitches with newer GDEs (Issue 48774)
- [r52729] Access GNOME Keyring on the main thread to fix a crash for some users (Issue 48343)
Known Issues
- PDF plugin does not load on Linux (Issue 49702)
More details about additional changes are available in the svn log of all revisions.
The Dev channel has been updated to 6.0.466.0 for Windows and Linux
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.
Dev Channel Update
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)


