Chrome 67: wider Site Isolation roll out - gHacks Tech News

Chrome 67: wider Site Isolation roll out

Google started the roll out of Google Chrome 67, a new version of the company's web browser, today. The new version of Chrome is a security release first and foremost.

Google Chrome users on the desktop can run manual checks for updates to get the browser update right away; considering that Chrome 67 fixes 34 security issues, several of them rated as high, the second highest rating after critical, it is important that users update the browser to the new version as soon as possible.

Just load chrome://settings/help in the Chrome address bar to run a manual check for update. Please note that this works only on desktop versions of Chrome and not mobile versions. Unless you download and install Chrome 67 from mirror sites that are not official, you have to wait for Google to distribute the browser to your device.

google chrome 67

Google continues the roll out of Site Isolation in Chrome. The feature landed in Chrome 63 but it was turned off initially as Google wanted to test the functionality on a small subset of users before it widened the audience.

Site Isolation, or Strict Site Isolation, limits render processes to individual sites. Instead of handling multiple sites in a single render process, Chrome will move any additional site loaded on a website in its own process. Sites can be loaded using iframes and other means.

Site Isolation improves stability and security but it comes at the cost of increased memory usage. Google stated that initial tests showed that memory usage might increase by up to 20%.

Google enabled the feature for part of the Chrome userbase but it included an experimental flag in the browser which provided anyone with the option to enable it in Chrome (check out the linked article above for instructions).

Chrome users who have been selected for the Site Isolation trial may disable it in the following ways:

  1. Set chrome://flags#enable-site-per-process to disabled if you enabled the feature using the flag.
  2. Set chrome://flags#site-isolation-trial-opt-out to "Opt-out (not recommended)" if you have been selected for the trial.

Google notes that users may run into issues when they try to load certain sites in Chrome. Another reason for wanting to disable Site Isolation is the increase in memory usage. If you notice Chrome's memory usage going way up, you may want to check if the feature has been enabled for the installation.

Chrome 67 features plenty of under-the-hood changes. You find some of them mentioned on the official Chromium Blog (focusing on Developer additions); notable additions are inclusion of a Generic Sensor API to work with sensors such as accelerometers, gyroscopes, or motion sensors, the new WebXR Device API for AR and VR experiences, and support for the Web Authentication API.

Related articles

Summary
Chrome 67: wider Site Isolation roll out
Article Name
Chrome 67: wider Site Isolation roll out
Description
Google started the roll out of Google Chrome 67, a new version of the company's web browser, today. The new version of Chrome is a security release first and foremost.
Author
Publisher
Ghacks Technology News
Logo

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:

Comments

  1. Memory's price going up said on May 30, 2018 at 5:19 pm
    Reply

    What if a website loads up 100 of iframes of tracking’n’stuff? Will it load 100 content processes? RIP my memory. I think I may just switch to good old Firefox’n’noscript when I’m not using the Tor Browser.

    1. preddit said on May 30, 2018 at 6:33 pm
      Reply

      (Soon) How to scam Chrome users: make a tech support scam webpage that loads 3k iframes and tell them their system needs a mem cleanup. 3k$ a day guaranteed.

      Chrome security team: But muuh we need to mitigate against Meltdown/Spectre in the software instead of telling Intel/AMD to fix their backdoored ME/PSP performance-first security-last spying silicon pieces!!

  2. Bobby Phoenix said on May 30, 2018 at 8:03 pm
    Reply

    I have been switching between Chrome and Firefox for a long time. Usually just switching things up to check the newest releases, and the use for me has been about 50/50 until recently. The last couple of Chrome release have really changed things for me for the worse. I find myself using Firefox more, and I am quite happy with it. I don’t know what Google it trying to do with Chrome, but for me the browsers have flipped. Chrome was the overall choice if I had to choose, but now it’s Firefox.

    1. Anonymous said on June 16, 2018 at 5:41 am
      Reply

      As you can see according to this article Google is being very clear on what it’s trying to do with Chrome (adding strict site isolation for example). If anything, the last couple of Firefox releases are what have changed things for the worse.

      Browser marketshare for FF has been plummeting thanks to Mozilla’s decisions to transition to a far less powerful WebExtension system, adding tracking scripts to its add-on page, etc.

  3. Richard Allen said on May 30, 2018 at 8:08 pm
    Reply

    “Google stated that initial tests showed that memory usage might increase by up to 20%.”
    From what I’m seeing that is some seriously wishful thinking. I need to test it more but… On android central I saw up to 18 subframes, if you then open business insider and forbes, all three at the same time, you will have then won the content process jackpot.
    Screenshot – 3 tabs using 2.7GB of memory without even scrolling the pages, no content blocking enabled:
    https://s33.postimg.cc/4izobgqn3/Chrome_Three_Tabs.png

    With Chrome Stable I opened one tab to an article on PCWorld. Not using any content blocking I saw 13 subframes using about 750MB of memory. The total browser memory use was about 1.34GB, for one tab. Total memory use did not include uBO and Privacy Possum because they were disabled on the site.
    Screenshot – one tab no content blocking:
    https://s33.postimg.cc/bpwrtg6zj/Chrome_Site_Isolation.png

    I’m thinking that the higher memory use will push people into using some type of content blocking, disabling site isolation with a flag, or moving to a different browser. Is having 4GB of system memory going to be enough to run Chrome with more than three tabs open? On PCWorld with content blocking Enabled, the subframe count went from 13 to 2, with my uBO setup that is globally blocking 3rd-party frames, the subframe count went down to 1. Most importantly, content blocking will significantly reduce the memory use when site isolation is enabled.

    What I’ve been doing with Chrome Dev and Stable is to have site isolation disabled with the “opt-out” flag and the desktop shortcuts are using the site-per-process command line switch. So, if I open either one with the ‘taskbar shortcut’ the result will be no site isolation, opening the ‘desktop shortcut’ results in site isolation working. I have plenty of memory so I might change that setup in the future to use site isolation all the time, but right now I don’t care one way or the other, Chrome is not my primary.

    1. Martin Brinkmann said on May 30, 2018 at 8:29 pm
      Reply

      I just checked Chrome Stable with Site Isolation enabled, and it used a lot of RAM (about 3.1 Gigabytes of it). The machine has 32 Gigabytes of RAM so no issue yet on that end but if you run Chrome on a machine with 4 Gigabytes or even less, I’d imagine that things may not run as smooth anymore with the feature enabled.

      1. Bobby Phoenix said on May 30, 2018 at 9:05 pm
        Reply

        You’re spot on. About the same amount for me. And I just upgraded my RAM from 4 to 8 recently, and now Chrome cancels it right out. Great!

      2. Richard Allen said on May 30, 2018 at 9:55 pm
        Reply

        I don’t like opening pages without content blocking enabled but decided to risk one more test for the team. At least I’m using a small malware hosts file. ;)

        Anyway, with content blocking disabled, I opened 12 tabs, one being the Startpage search engine, so that tab was a freebie. Did not scroll any pages and stayed on page only until it was done loading. I saw “61” chrome processes in the Windows Task Manager and it was using 5.5GB of RAM. If I tried, I don’t think it would be that hard to use 8GB but then I would be sweating bullets worrying about ruining my 10 year record of being malware free. Nuf said. LoL

      3. Martin Brinkmann said on May 30, 2018 at 10:14 pm
        Reply

        The content blocking is probably preventing some processes that would otherwise be created so that overall RAM use is not as high.

      4. Richard Allen said on May 31, 2018 at 6:09 pm
        Reply

        @Martin
        “Chrome users who have been selected for the Site Isolation trial may disable it in two ways:”
        Just noticed that is Not what I’m seeing. I have for some time now, had the flag “Site isolation trial opt-out” set to “Opt-out (not recommended)”. Since my Chrome install was chosen for the trial, the only way I can disable site isolation is with the “Opt-out” flag, the flag for “Strict site isolation” is already set to “Disabled” which for me is the default setting for that flag. Screenshot shows my default flag settings and site isolation is working. Looks to me like the only way to really tell is to open e.g. Forbes or IMDb then look to see in the chrome task manager if there is a subframe process, if there is then site isolation is enabled. The following link has a “Verifying” section also for anyone interested: “https://www.chromium.org/Home/chromium-security/site-isolation”
        Screenshot:
        “https://s33.postimg.cc/cgvgzj0tr/Site_Isolation_Working_with_Default_Flag_Settings.png”

        I wanted to be able to visualize the memory use with content blocking enabled or not, and with site isolation enabled or not.
        Memory use with 12 Tabs, most of which can have subframe processes when using site isolation:
        No Content Blocking + Site Isolation = 4.97GB
        No Content Blocking — No Site Isolation = 3.65GB
        Content Blocking + Site Isolation = 1.63GB
        Content Blocking — No Site Isolation = 1.38GB

      5. Martin Brinkmann said on May 31, 2018 at 7:09 pm
        Reply

        Richard, thanks for the info. I have updated the article to reflect your experience.

      6. Richard Allen said on May 30, 2018 at 10:04 pm
        Reply

        Just to be clear, Chrome by itself was using 5.5GB of RAM, total used by system was 7.7GB. This desktop has 16GB.

  4. Google Is Hunting Your RAM said on May 30, 2018 at 8:49 pm
    Reply

    Firefox Nightly+WebRender For the Win!

    I’ll say it but Chrome is turning into trash can showdown with all the memory usage, it’s now IMPOSSIBLE to use it with a 3Go notebook that I have.

  5. pHROZEN gHOST said on May 30, 2018 at 9:24 pm
    Reply

    I am sure PC and RAM manufacturers are loving what Google is doing. This makes you wonder …

    1. coakl said on June 1, 2018 at 2:21 am
      Reply

      And don’t forget the Spectre/Meltdown security scare. Systems with Haswell (4th-gen) or older CPU’s are slowed down by both the Windows and microcode/BIOS patches.

      Put two and two together…and it seems like an agreement between Microsoft, Google, and Intel to *slow down* older Win 7 systems with limited memory.
      And *encourage, force, drag* people into buying NEW systems with Win 10.
      Criminal conspiracy? Normal evil corporate behavior?
      Whatever it is, those three companies are benefiting financially from these so-called “patches” and “upgrades.”

  6. Kubrick said on May 30, 2018 at 9:37 pm
    Reply

    Quite odd as i have chrome installed on my linux PC and it hardly ever uses more than 500mb of ram and this is with site isolation enabled.

    1. Martin Brinkmann said on May 30, 2018 at 9:50 pm
      Reply

      It depends a lot, probably, on what you do on the Internet.

    2. gef950 said on May 31, 2018 at 3:35 am
      Reply

      On Ubuntu, chrome seems to use less memory than firefox.

  7. John said on May 31, 2018 at 12:12 am
    Reply

    Been my experience that it eats up a lot of RAM doing this site isolation. If your a person who likes lot’s and lot’s of tabs opened, site isolation is not for you. I have 8 Gb RAM and with only 6 tabs open I was at 70% of my RAM consumption. Much of that was Chrome not Windows. Also Chrome 67 seems to create a lot of CPU cycles at times too. I noticed my fan which hardly ever is noticeable running at times. Cannot pin it down, but something with Java script or Ajax. Edge right now is much more plausible as a lower resource browser then Chrome.

  8. Anonymous said on May 31, 2018 at 1:21 am
    Reply

    Does anyone know if the builds from https://chromium.woolyss.com/ are safe?

    1. ShintoPlasm said on May 31, 2018 at 9:51 am
      Reply

      Why wouldn’t these builds be safe? That website has a long-standing good reputation as a provider of clean Chromium builds.

  9. shawross said on June 1, 2018 at 2:08 am
    Reply

    I have the new 67 version of chrome and I am using 64 bit Windows 7 with 6 GB ram.

    With 4 tabs open and site isolation I am only using 1.6 GB ram with CPU 4%.

    Sweet

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.