Labels:


Labels:


If you find new issues, please let us know by filing a bug. Want to change to another Chrome release channel? Find out how.

Jason Kersey
Google Chrome
Labels:

Labels:

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.
  • [64-bit Linux only] [56449] High Bad validation for message deserialization on 64-bit builds. Credit to Lei Zhang of the Chromium development community.
  • [60761] Medium Bad extension can cause browser crash in tab handling. Credit to kuzzcc.
  • [63529] Low Browser crash with NULL pointer in web worker handling. Credit to Nathan Weizenbaum of Google.
  • [$1000] [63866] Medium Out-of-bounds read in CSS parsing. Credit to Chris Rohlf.
  • [$1000] [64959] High Stale pointers in cursor handling. Credit to Sławomir Błażek and Sergey Glazunov.
Full details about the Chrome changes are available 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.

Jason Kersey
Google Chrome
Labels: ,



The scrolling regression has been fixed (Issue: 66079).


Update: The Dev channel has been updated to 9.0.597.15 for Windows, Mac, Linux, and Chrome Frame


There is a regression in 9.0.597.15 where scrolling up does not work using the mouse wheel (Issue: 66079) a fix is underway and will be released in short order.


--


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

All
Known Issue:
  • Regression: Certain sites fail to render the first time.  The temporary workaround is to re-load the page. (Issue: 65376)
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.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

Anthony Laforge
Google Chrome
Share on Twitter Share on Facebook
Labels:

Share on Twitter Share on Facebook
Labels: ,

Labels:

Labels:

Labels:

Labels:

Share on Twitter Share on Facebook
Labels:

Labels:

Labels:

Labels:

Share on Twitter Share on Facebook
Labels:

Labels:

Share on Twitter Share on Facebook
Labels:

Share on Twitter Share on Facebook
Labels:

Labels:


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.

  • [48225] [51727] Medium Possible autofill / autocomplete profile spamming. Credit to Google Chrome Security Team (Inferno).
  • [48857] High Crash with forms. Credit to the Chromium development community.
  • [50428] Critical Browser crash with form autofill. Credit to the Chromium development community.
  • [$500] [51680] High Possible URL spoofing on page unload. Credit to kuzzcc; plus independent discovery by Jordi Chancel.
  • [53002] Low Pop-up block bypass. Credit to kuzzcc.
  • [53985] Medium Crash on shutdown with Web Sockets. Credit to the Chromium development community.
  • [Linux only] [54132] Low Bad construction of PATH variable. Credit to Dan Rosenberg, Virtual Security Research.
  • [$500] [54500] High Possible memory corruption with animated GIF. Credit to Simon Schaak.
  • [Linux only] [54794] High Failure to sandbox worker processes on Linux. Credit to Google Chrome Security Team (Chris Evans).
  • [56451] High Stale elements in an element map. Credit to Michal Zalewski of the Google Security Team.
In addition, we would like to credit Aki Helin of OUSPG and kuzzcc for finding bugs during the development cycle such that they never reached a stable build.
Share on Twitter Share on Facebook
Labels: