Google Chrome, Google’s new web browser, just reached version 5.0.375.70 for the Mac. The new version, an 25.2 megabyte download, offers the following the following changes:
– Medium: Cross-origin keystroke redirection. Credit to Michal Zalewski of Google Security Team.
– High Cross-origin bypass in DOM methods. Credit to Sergey Glazunov.
– High: Memory error in table layout. Credit to wushi of team509.
– High: Linux sandbox escape. Credit to Mark Dowd under contract to Google Chrome Security Team.
– High: Bitmap stale pointer. Credit to Mark Dowd under contract to Google Chrome Security Team.
– High: Memory corruption in DOM node normalization. Credit to Mark Dowd under contract to Google Chrome Security Team.
– High: Memory corruption in text transforms. Credit to wushi of team509.
– Medium: XSS in inner HTML property of text area. Credit to sirdarckcat of Google Security Team.
– High: Memory corruption in font handling. Credit: Apple.
– High: Geolocation events fire after document deletion. Credit to Google Chrome Security Team (Justin Schuh).
– High: Memory corruption in rendering of list markers. Credit: Apple.
Google Chrome requires Mac OS X 10.5 or later and an Intel-based Mac to install and run.
If you’ve played with it and have an opinion, let us know what you think in the comments.
2 replies on “Google Chrome 5.0.375.70 out the door”
snappier than firefox, but a lot more crash happy =-
chrome gets unstable around 40 tabs total on my computer
while firefox is good for around 70
but safari doesn't play well with more than 8 tabs 🙁
i'm just starting to use opera again, and its perfectly happy being a youtube music player 🙂 but it has the annoying habit of having a page-load delay 😡
bu
Chrome seems to have issue with font rendering on the Mac. I often see what looks like squares with a capital “A” inside of it rather than the text of the page. Opening these pages in other browsers (FF, Safari) I see the pages with fonts intact displaying normally. It appears to relate to which fonts are activated on my Mac. I've corrected the problem by using Font Book to find and fix font duplicates but sometimes this doesn't work.