Google Chrome 66 official release, fix security flaws

Google has officially launched the official version of Google Chrome 66.0.3359.117 on all supported platforms (Windows, Mac, and Linux). The new version introduces the “Site Isolation Trial”, video autoplay blocking capability and fix 62 security flaws.

In addition to fixing a series of third-party reported security issues, the Chrome 66 official release has enabled a trial of Site isolation trial opt-out for a small percentage of Chrome users.

One of the new features of Chrome 66 is to be able to better handle automatically played video on the site. When a video with audio is automatically played on a web page, it will block the video playback, but the browser will not interfere with the audio. Video plays automatically.

However, there are exceptions to the rules, and the main rule used by Chrome 66 is to determine whether to play a video with the sound based on the website’s “Media Engagement Index”.

Basically, if you have previously interacted with the site or played media, videos with sound may still play automatically.

You can check chrome://media-engagement/ in your browser to see how each rating of Chrome 66 is released for each site.

Chrome’s multi-process architecture was introduced with the release of browsers, which increases browser security and stability at the expense of computer memory. As the attacker interacts with content in other processes more and more difficult, security is improved and stability is improved.

Chrome’s default multi-process system can still share processes. If you navigate to multiple different web pages in a single tab, they may be opened in the same process (as are embedded web pages using iframes). This means that irrelevant sites or pages may share a process.

Site Isolation is a new experimental feature of Google Chrome 66 that ensures that a process is limited to pages from one site. That is, as long as Site Isolation is enabled, Chrome will create a new process when the user visits any domain name.

This will further increase the security and stability of Chrome, and of course, at the expense of additional memory footprint. Because Chrome generates more processes, depending on browser usage, memory usage may increase by 20% or more when strict site isolation is enabled.