Chrome 67 has enabled Site Isolation on Windows, Mac, Linux, and Chrome OS, which increases memory usage by 10-13% and introduces some problems for web developers:
beforeunload
event handlers are not working in cross-site subframes and unload
event handlers may have issues with postMessage
,I want to save RAM more than extra security. How to disable Site Isolation?
You can also try opting out of field trials of Site Isolation to diagnose bugs, by visiting chrome://flags#site-isolation-trial-opt-out, choosing "Disabled (not recommended)," and restarting.
Starting in Chrome 92, Site Isolation will treat non-default values of the COOP header on any document as a signal that the document's underlying site may have sensitive data and will start isolating such sites.
The isolation mode gives developers more focus on a container and its contained offspring. This includes: Special overlay to highlight the container on the inspected page. Blur/mask the non-container area to bring more focus to the container.
According to the docs, you can disable Site Isolation by adding Chrome command line switch:
chrome.exe --disable-features=IsolateOrigins,site-per-process
Another way is to go to chrome://flags/#site-isolation-trial-opt-out
and select Opt out
.
In Chrome 68+, you can go to chrome://process-internals
to verify that Site Isolation is disabled.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With