Google heeft met versienummer 10.0.648.127 een nieuwe stabiele uitgave van zijn webbrowser Chrome de deur uit gedaan. Google Chrome is beschikbaar in drie verschillende uitvoeringen, te weten stable, bèta en dev. Developmentversies zitten in een vroeg stadium van ontwikkeling en zijn dus het minst stabiel. In versie 10 treffen we onder andere de nieuwe en snellere Javascript-engine Crankshaft aan, is de beveiliging aangescherpt, draait Adobe Flash in een afgeschermde omgeving onder Windows en kunnen webapps nu op de achtergrond draaien. Het volledige changelog van deze release ziet er als volgt uit:
Chrome Stable Release
The Google Chrome team is excited to announce the arrival of Chrome 10.0.648.127 to the Stable Channel for Windows, Mac, Linux, and Chrome Frame. Chrome 10 contains some really great improvements including:Security fixes and rewards:
- New version of V8 - Crankshaft - which greatly improves javascript performance
- New settings pages that open in a tab, rather than a dialog box
- Improved security with malware reporting and disabling outdated plugins by default
- Sandboxed Adobe Flash on Windows
- Password sync as part of Chrome Sync now enabled by default
- GPU Accelerated Video
- Background WebApps
- webNavigation extension API
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.We would also like to thank Ben Hawkes of the Google Security Team, Sergey Glazunov, Martin Barbella and “temp01irc” for working with us during the development cycle and helping prevent bugs from ever reaching the stable channel.
- Possible to navigate or close the top location in a sandboxed frame.
- [Linux only] Work around an X server bug and crash with long messages.
- [Linux only] Possible browser crash with parallel print()s.
- Cross-origin error message leak.
- Memory corruption with counter nodes.
- Stale node in box layout.
- Cross-origin error message leak with workers.
- Use after free with DOM URL handling.
- Out of bounds read handling unicode ranges.
- Same origin policy bypass in v8.
- Pop-up blocker bypasses.
- Use-after-free in document script lifetime handling.
- Out-of-bounds write in the OGG container.
- Stale pointer in table painting.
- Use of corrupt out-of-bounds structure in video code.
- Crash with the DataView object.
- Bad cast in text rendering.
- Stale pointer in WebKit context code.
- Leak of heap address in XSLT.
- Stale pointer with SVG cursors.
- DOM tree corruption with attribute handling.
- Corruption via re-entrancy of RegExp code.
- Invalid memory access in v8.
Last, but not least, we’d like to offer special thanks to Christian Holler. This is for working with us on his grammar-based fuzzing project, resulting in a more stable and secure “Crankshaft” engine for v8.
More on what's new at the Official Chrome Blog. You can find full details about the changes that are in Chrome 10 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.