912 posts in this topic

Dev Channel Update

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

All

  • Updated V8 - 3.13.7.1
  • Fixed playback of multiple audio streams with Pepper Flash, WebRTC, and WebAudio.
  • Fixed crash when attempting to play audio without a sound card or via remote desktop.
  • Media Galleries Extension API should work on all platforms, though permission format has changed.
  • Chrome will automatically check for captive portals when showing SSL interstitials or when an HTTP server responds to an HTTPS request.

Windows

  • Now Chrome on Windows 8 uses a single profile regardless if running on desktop or metro mode. A new menu item has been added to switch mode which cause a relaunch.

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....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.com/p/chromium/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

Dev Channel Update

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

All

  • Updated WebKit - 537.11
  • Fixed simultaneous audio playback is broken (Issue: 150003)
  • Fixed bug with Web Intents and non-sticky defaults (Issue: 148740)
  • Audio may drop out under certain play / pause cycles. (Issue: 150702)

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

You can find out about getting on the Dev channel here: http://dev.chromium....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

Stable Channel Update

The Chrome Team is excited to announce the promotion of Chrome 22 to the stable channel. Chrome 22.0.1229.79 (also now available on the beta channel) has a number of new and exciting updates including:

  • Mouse Lock API availability for Javascript
  • Additional Windows 8 enhancements
  • Continued polish for users of HiDPI/Retina screens

You can find out more about Chrome 22 on the Official Chrome Blog.

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.

Occasionally, we issue special rewards for bugs outside of Chrome, particularly where the bug is very severe and/or we are able to partially work around the issue:

  • [$5000] [146254] Critical CVE-2012-2897: Windows kernel memory corruption. Credit to Eetu Luodemaa and Joni V?h?m?ki, both from Documill.

And back to your regular scheduled rewards, including some at the new higher levels:

  • [$10000] [143439] High CVE-2012-2889: UXSS in frame handling. Credit to Sergey Glazunov.
  • [$5000] [143437] High CVE-2012-2886: UXSS in v8 bindings. Credit to Sergey Glazunov.
  • [$2000] [139814] High CVE-2012-2881: DOM tree corruption with plug-ins. Credit to Chamal de Silva.
  • [$1000] [135432] High CVE-2012-2876: Buffer overflow in SSE2 optimizations. Credit to Atte Kettunen of OUSPG.
  • [$1000] [140803] High CVE-2012-2883: Out-of-bounds write in Skia. Credit to Atte Kettunen of OUSPG.
  • [$1000] [143609] High CVE-2012-2887: Use-after-free in onclick handling. Credit to Atte Kettunen of OUSPG.
  • [$1000] [143656] High CVE-2012-2888: Use-after-free in SVG text references. Credit to miaubiz.
  • [$1000] [144899] High CVE-2012-2894: Crash in graphics context handling. Credit to S?awomir B?a?ek.
  • [Mac only] [$1000] [145544] High CVE-2012-2896: Integer overflow in WebGL. Credit to miaubiz.
  • [$500] [137707] Medium CVE-2012-2877: Browser crash with extensions and modal dialogs. Credit to Nir Moshe.
  • [$500] [139168] Low CVE-2012-2879: DOM topology corruption. Credit to pawlkt.
  • [$500] [141651] Medium CVE-2012-2884: Out-of-bounds read in Skia. Credit to Atte Kettunen of OUSPG.
  • [132398] High CVE-2012-2874: Out-of-bounds write in Skia. Credit to Google Chrome Security Team (Inferno).
  • [134955] [135488] [137106] [137288] [137302] [137547] [137556] [137606] [137635] [137880] [137928] [144579] [145079] [145121] [145163] [146462] Medium CVE-2012-2875: Various lower severity issues in the PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [137852] High CVE-2012-2878: Use-after-free in plug-in handling. Credit to Fermin Serna of Google Security Team.
  • [139462] Medium CVE-2012-2880: Race condition in plug-in paint buffer. Credit to Google Chrome Security Team (Cris Neckar).
  • [140647] High CVE-2012-2882: Wild pointer in OGG container handling. Credit to Google Chrome Security Team (Inferno).
  • [142310] Medium CVE-2012-2885: Possible double free on exit. Credit to the Chromium development community.
  • [143798] [144072] [147402] High CVE-2012-2890: Use-after-free in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [144051] Low CVE-2012-2891: Address leak over IPC. Credit to Lei Zhang of the Chromium development community.
  • [144704] Low CVE-2012-2892: Pop-up block bypass. Credit to Google Chrome Security Team (Cris Neckar).
  • [144799] High CVE-2012-2893: Double free in XSL transforms. Credit to Google Chrome Security Team (Cris Neckar).
  • [145029] [145157] [146460] High CVE-2012-2895: Out-of-bounds writes in PDF viewer. Credit to Mateusz Jurczyk of Google Security Team, with contributions by Gynvael Coldwind of Google Security Team.
  • [Linux only] [137541] Critical CVE-2012-2859: Crash in tab handling. Credit to Jeff Roberts of Google Security Team.
  • [137671] Medium CVE-2012-2860: Out-of-bounds access when clicking in date picker. Credit to Chamal de Silva.

Many of the above bugs were detected using AddressSanitizer.

We?d also like to thank Arthur Gerkis for working with us during the development cycle and preventing security regressions from ever reaching the stable channel.

Full details about what's in this release are available in the SVN revision log. Found a bug? Report it! On a different channel, but want to join us on the Beta train? The Chromium wiki has you covered.

Jason Kersey

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

Stable Channel Update

you beat me to it.

Share this post


Link to post
Share on other sites

I think it's great how developers get paid for fixing high problem bugs!

Share this post


Link to post
Share on other sites

Stable channel update today is excellent, it fixed several annoying bugs I was having in the linux version (<< malware site >> packet loss test always failed, even with java plugin installed and working, chrome:plugins said java needed a critical security update even when it was fully up to date, and in gnome 3 setting "use system titlebar" made titlebar buttons disappear)

EDIT: WTF neowin? p i n g t e s t.net is not a malware site...

Share this post


Link to post
Share on other sites

Dev Channel Update

The Dev channel has been updated to 23.0.1271.6 for (All|Windows|Mac|Linux|ChromeFrame) platforms

All

  • Updated V8 - 3.13.7.2
  • Several fixes to forced compositing mode (Issues: 150881, 157920)
  • Fixed known crashers (Issue: 146689, and several audio ones.)

Windows

  • Fixed path lengths for storage partitions (Issue: 151450)
  • Fixed CJK input for Metro mode (Issue: 149136)

Linux

  • Fixed WebRTC audio (Issue: 150570)

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....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

Dev Channel Update

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

This build fixes several known crashes as well as:

  • Win8: Fixed Pre-edit character appears when bringing up the Touch keyboard (Issue: 151587)
  • Mac: Flash timezone issue is fixed (Issue: 149006)

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....ved/dev-channel.

If you find new issues, please let us know by filing a bug at http://code.google.c...um/issues/entry

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

Beta Channel Update

The Chrome team is happy to announce the arrival of Chrome 23.0.1271.10 to the Beta Channel for Windows, Mac, Linux, and Chrome Frame.

Chrome 23 contains some really great improvements including better communication and media experiences. More on what's new at the Chromium Blog.

You can find full details about the changes that are in Chrome 23 in the SVN revision log. If you find new issues, please let us know by filing a bug. Want to change to another Chrome release channel? Find out how.

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

The re-introduced zoom status icon is less annoying now (no longer steals focus) which is great.

I also like the new ruler that appears when inspecting elements but wish there was a something under Developer tools settings to keep it visible while Deveoper tools is being used.

post-101313-0-16824500-1349236779.png

Share this post


Link to post
Share on other sites

What has Google done to the new font rendering mechanism? Fonts look a little bit lighter and condensed when compared to other GDI-rendering browsers (the ones not using HWA). Is it a new step to support DirectWrite rendering?

Share this post


Link to post
Share on other sites

Dev Channel Update

The Dev channel has been updated to 24.0.1284.2 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:

All

  • Updated V8 - 3.13.7.1
  • Updated WebKit - 537.13
  • Fixed an issue where clearing browsing data would not complete when Pepper Flash was disabled (Issue: 144874)
  • Fixed an issue where inline disposition isn?t displaying correctly. (Issue: 145622)
  • Fixed a crash when clicking speech input. (Issue: 146689)
  • Fixed file system URLs no longer work in platform apps. (Issue: 150861)
  • Fixed a crash when opening YouTube in full screen mode. (Issue: 149821)
  • Fixed a crash when loading explicit intent service. (Issue: 150834)

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

What has Google done to the new font rendering mechanism? Fonts look a little bit lighter and condensed when compared to other GDI-rendering browsers (the ones not using HWA). Is it a new step to support DirectWrite rendering?

Yep, updated a few days ago and it looks ridiculous to my eyes.

Oh why are there not any decent font rendering extensions for Chrome :/

Share this post


Link to post
Share on other sites

Fonts look fine on Chrome, and always have with the rare exception of a bug here and there

Share this post


Link to post
Share on other sites

Yep, updated a few days ago and it looks ridiculous to my eyes.

Oh why are there not any decent font rendering extensions for Chrome :/

I wish they could do something like IE 9. Best font rendering ever!

Share this post


Link to post
Share on other sites

Beta Channel Update

The Beta channel has been updated to 23.0.1271.17 for Windows, Mac, Linux, and ChromeFrame. This build fixes some of the known stability issues. A complete log of what changed can be found in the svn revision log. If you find new issues, please let us know by filing a bug. Want to change to another Chrome release channel? Find out how.

Karen Grunberg

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

as it's about updates in chrome thought this might be the best place to ask is there any way to get chrome to alert and ask me about updating just i like to have a landmark of sorts in time to help with trouble shooting.

Share this post


Link to post
Share on other sites

as it's about updates in chrome thought this might be the best place to ask is there any way to get chrome to alert and ask me about updating just i like to have a landmark of sorts in time to help with trouble shooting.

No it's supposed to self update without warning

Share this post


Link to post
Share on other sites

Stable Channel Update

Monday, October 8, 2012 | 10:00

Labels: Stable updates

The Stable channel has been updated to 22.0.1229.92 for Windows, Mac, and Linux. This update contains a number of stability fixes, including an issue with multiple profiles on Mac OS X 10.8.2. It also contains a fix for text display on the Mac, as well as the security updates listed below.

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.

[$1000] [138208] High CVE-2012-2900: Crash in Skia text rendering. Credit to Atte Kettunen of OUSPG.

[$3133.7] [147499] Critical CVE-2012-5108: Race condition in audio device handling. Credit to Atte Kettunen of OUSPG.

[$500] [148692] Medium CVE-2012-5109: OOB read in ICU regex. Credit to Arthur Gerkis.

[151449] Medium CVE-2012-5110: Out-of-bounds read in compositor. Credit to Google Chrome Security Team (Inferno).

[151895] Low CVE-2012-5111: Plug-in crash monitoring was missing for Pepper plug-ins. Credit to Google Chrome Security Team (Chris Evans).

Share this post


Link to post
Share on other sites

Dev Channel Update

The Dev channel has been updated to 24.0.1290.1 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:

All

  • Fixed issue where clearing browse data never completes with PPAPI flash plugin disabled. [issue: 144874]
  • Fixed issue in disabling sync for default apps. [issue: 152582]
  • Fixed crashes 154167, 153902, 152622.

Known Issues

  • Issue 154663: On Windows 8, if Chrome is set to use Windows 8 mode, it might launch in Windows 8 mode when trying to uninstall (and therefore fail to uninstall). Workaround: make another browser default (in Control Panel -> Default Programs) and then uninstall Chrome.

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

60k??

Stable Channel Update

Wednesday, October 10, 2012 | 08:40

Labels: Stable updates

The Stable channel has been updated to 22.0.1229.94 for Windows, Mac, and Linux. This release contains fixes for the security issue listed below.

Security fixes and rewards:

Congratulations to Pinkie Pie, returning to the fray with another beautiful piece of work!

We?re delighted at the success of Pwnium 2, and anticipate additional hardening and future improvements to Chrome as a result of the competition.

  • [$60,000][154983][154987] Critical CVE-2012-5112: SVG use-after-free and IPC arbitrary file write. Credit to Pinkie Pie.

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.

Full details about what's in this release are available in the SVN revision log. Found a bug? Report it! On a different channel, but want to join us on the Beta train? The Chromium wiki has you covered.

Share this post


Link to post
Share on other sites

I'm wondering when they'll be updating the bookmark folder icons on the Windows version to a more modern looking icon. They've got "Windows 98" written all over them. Why not have it like the OSX version? Why not recolor those into having the same color as the OS's folder icons?

Share this post


Link to post
Share on other sites

Dev Channel Update

The Dev channel has been updated to 24.0.1297.0 for Windows, Mac, Linux, and Chrome Frame. This build contains following updates:

All

  • Updated V8 - 3.14.4.1
  • Updated WebKit - 537.16
  • Fixed tab character in text field when pressed Tab in a <browser> tag. (Issue: 149859)

  • Fixed omnibox suggestion: restore selection on WM_IME_ENDCOMPOSITION (Issue: 154379)
  • Fixed text that goes out of the box under Related section after an app was installed. (Issue: 154797)
  • Fixed Web Store icon (Issue: 149887)

Windows

  • Updated styling for Web Intents windows
  • Setting preference to launch in Metro on Windows 8 will no longer cause Chrome to launch in Metro mode upon uninstall.
  • Fixed missing print preview on Asian sites. (Issue: 161704)

Mac

  • Fixed a bug where Chrome would use an outdated version of Pepper Flash (Issue: 151716)
  • [r161874] Fixed a bug where Chrome would fail to quit if at least two windows were open and a page had a beforeunload handler (Issue: 118424)
  • Fixed browser hang when webcam used on facebook with OSX flapper. (Issue: 152757)

Full details about what changes are in this build are available in the SVN revision log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug.

Dharani Govindan

Google Chrome

Source: Google Chrome Releases blog

Share this post


Link to post
Share on other sites

I'm wondering when they will fix the font rendering issue. Since Chrome v22 actually... either they are too thin or too bold depending of the websites.

Share this post


Link to post
Share on other sites

I'm wondering when they will fix the font rendering issue. Since Chrome v22 actually... either they are too thin or too bold depending of the websites.

Have an example screenshot?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.