Chrome's method of protecting against Spectre uses more RAM
Google's Chrome browser is better equipped to protect against side-channel attacks, but it comes at a cost.
Keep up to date with the most important stories and the best deals, as picked by the PC Gamer team.
You are now subscribed
Your newsletter sign-up was successful
Want to add more newsletters?
Every Friday
GamesRadar+
Your weekly update on everything you could ever want to know about the games you already love, games we know you're going to love in the near future, and tales from the communities that surround them.
Every Thursday
GTA 6 O'clock
Our special GTA 6 newsletter, with breaking news, insider info, and rumor analysis from the award-winning GTA 6 O'clock experts.
Every Friday
Knowledge
From the creators of Edge: A weekly videogame industry newsletter with analysis from expert writers, guidance from professionals, and insight into what's on the horizon.
Every Thursday
The Setup
Hardware nerds unite, sign up to our free tech newsletter for a weekly digest of the hottest new tech, the latest gadgets on the test bench, and much more.
Every Wednesday
Switch 2 Spotlight
Sign up to our new Switch 2 newsletter, where we bring you the latest talking points on Nintendo's new console each week, bring you up to date on the news, and recommend what games to play.
Every Saturday
The Watchlist
Subscribe for a weekly digest of the movie and TV news that matters, direct to your inbox. From first-look trailers, interviews, reviews and explainers, we've got you covered.
Once a month
SFX
Get sneak previews, exclusive competitions and details of special events each month!
The latest version of Google's Chrome browser implements a mechanism designed to protect users from speculative execution side-channel attacks like Spectre, but there is a performance trade-off—it uses more system memory than before.
That is an unfortunate (if perhaps necessary) side effect for the benefit of added security. The feature is called "Site Isolation" and is turned on by default in Chrome 67, whereas before Chrome users had to edit Chrome's flags to enable it.
"Site Isolation is a large change to Chrome's architecture that limits each renderer process to documents from a single site. As a result, Chrome can rely on the operating system to prevent attacks between processes, and thus, between sites," Google explains.
Chrome was born with a multi-process architecture where different tabs could use different renderer processes. However, the Site Isolation feature narrows the scope, limiting each renderer process to documents from at most one site.
"This means all navigations to cross-site documents cause a tab to switch processes. It also means all cross-site iframes are put into a different process than their parent frame, using 'out-of-process iframes'," Google adds.
Google said it's been working on this for several years, independently of Spectre, so the inclusion of Site Isolation was inevitable. The side effect is a 10-13 percent increase in memory overhead in real workloads, due to the increased number of renderer processes that Chrome now has to run, according to Google.
That's a pretty big hit to system memory, especially for a browser that has been known to have memory leak issues. However, the argument is that it's better than potentially compromising sensitive information.
Keep up to date with the most important stories and the best deals, as picked by the PC Gamer team.
As of Chrome 67, Site Isolation is enabled for 99 percent of users on Windows, Mac, Linux, and Chrome OS. Google is holding back the remaining 1 percent to "monitor and improve performance."
Paul has been playing PC games and raking his knuckles on computer hardware since the Commodore 64. He does not have any tattoos, but thinks it would be cool to get one that reads LOAD"*",8,1. In his off time, he rides motorcycles and wrestles alligators (only one of those is true).


