Google Chrome 8 Stable and Google Chrome 9 - Advanced Security

So, exactly today Google presented an update to the stable update branch of Google Chrome. The browser has reached 8 milestones (apparently, such a rate implies 0.8 according to the development of Google Chrome OS that is coming to an end) in full accordance with the accelerated schedule of new versions release. Judging by the content of the update, Google is concentrating on security, “scoring” 30% acceleration of the V8 JavaScript engine. What can be seen in the new Chrome?

The change log is:
■ PDF-viewer "driven" in the sandbox. That is, the possible unsafe content will not be able to disrupt the browser, much less harm the system. Although, it seems to me that disrupting the operation of the process and all related processes (in Chrome, the default scheme is “process per thread (that is, the domain and the opening from the tab) malicious code can.
■ Applications are now supported out of the box, without requiring the launch of additional parameters.
■ Added applications to sync
■ The WebKit engine has been updated to version 534.10, and the JavaScript processor to 2.4.9.14.
■ Closed a number of vulnerabilities, among which the series has the status of serious ( 1 , 2 , 3 and 4 )
■ About 800 fixes, full list of which can be found here .
You can download the browser from the official site .
The beta version has the same version number and the same innovations as the “stabilizer”.

As for the "nine", then there is also work with security, among which the most important feature is the use of Adobe Flash in the sandbox . After 3 months, Chrome users can forget about the constant vulnerabilities of the Flash Player marked End of the World Critical , beta users will be able to enjoy this feature for a month, and developers and other advanced browser users can already see this in dev and Canary builds. It should be noted that Google is very closely cooperating with Adobe , so the work on the built-in PDF reader and Flash goes so briskly. Let's hope that the pace will be maintained, because the flash drive into the sandbox is relevant only for the Windows platform.
If you see errors, then run the browser with the parameter --disable-flash-sandbox
Other innovations include intensive work on:
■ Graphical acceleration and WebGL
■ The HTML5 IndexedDB specification element
■ Picking all sorts of chips from Google Labs .
You can also download the dev version from the official site.

Naturally, all this is relevant for Chromium, except for the PDF-viewer, which will have to be screwed separately. Flash from 10.1, starting from revision 66022 , will automatically be executed in the sandbox.