Site Isolation Status - Enabled on desktop in M67!

[Charlie Reis]

Site Isolation dedicates renderer processes to individual sites to improve security.

Recent updates:

• Site Isolation has launched as a Spectre mitigation on desktop!  It has been enabled for 99% of Windows, Mac, Linux, and ChromeOS users in M67.  (We're keeping a 1% holdback to monitor performance.) As usual, see here for how to diagnose and report any issues.

• Added chrome://process-internals to M68 for verifying Site Isolation mode.

• Fixed many crashes (touchscreen gestures, printing, renderer kills with process-per-site).

• Fixed multiple hit testing bugs discovered post-launch.

• Fixed basic unload handlers in OOPIFs.

• Fixed process creation during session restore.

• Fixed navigation issues, including history.back() inside OOPIFs and cancellations due to replaceState.

• Fixed several DevTools issues, including emulated mobile device touch events, DOM storage, security panel, performance panel, error page inspection, and console menu indent.

• Fixed keyboard scrolling issue when an OOPIF has focus.

• Fixed autoplay issue affecting Google Slides.

• Fixed zoom jankiness with OOPIFs.

• Fixed another TouchAction issue for OOPIFs.

• Updated CORB console message, reduced console spam, and posted CORB info for web developers.

• Several Android updates:

• We are continuing to run Android Canary trials of SitePerProcess at 50% to gather performance data.  Half of these users are given a V8 low memory mode to gauge impact on memory overhead.

• Fixed several crashes.

In progress work:

• Monitoring and fixing post-launch functional bugs.

• Fixing beforeunload and additional unload issues for OOPIFs.

• Fixing input events in iframes with CSS 3D transforms.

• Fixing scroll bubbling issues for keyboard and ChromeOS touchpad.

• Improving performance of OOPIF hit testing.

• Fixing issues with <embed> detach and fallback content.

• Investigating issues with OOPIF printing and drag n drop.

• Fixing Android-specific OOPIF issues.

[Łukasz Bendig]

Great news! 

Have you also set limit of memory to enable the feature? I mean, do you use site-per-process-only-for-high-memory-clients too or is's enabled without restrictions?

[Charlie Reis]

Thanks!  We did not use a memory limit for Site Isolation itself.  (site-per-process-only-for-high-memory-clients was a fallback option that we did not end up using.)  We did set a 1GB memory limit for enabling the spare renderer process, which is a feature that helped with navigation latency on cross-process navigations to cached pages (especially back/forward).

It's worth noting that Site Isolation is enabled at the chrome/ layer, so it isn't turned on by default in content/ yet.  I'm working on another message to embedd...@chromium.org with more details for content/ embedders, which I'm hoping to send out later today if possible.

Thanks,

Charlie