Chrome is more secure on Android: Now it uses more RAM.
Maybe you could hope children are #playing in a sandbox, But did you know websites and apps can? A new #Chrome for Android Update creates a new function that places websites in their own sandbox and prohibits them from interacting. This behavior is triggered automatically on websites that request for any kind of login and is allowed to continue on these websites.
Chrome for Android version 77 introduces this new feature for many users, but, like most Google updates, all users will not immediately see it occur. Despite the dramatics of the update, it is always possible for this functionality to interfere with websites that plan to communicate with each other, but, since this feature has been tested in Chrome Beta and Canary #Chrome up to now, it should not be a pronounced problem.
Isolating sites in a sandbox ensures that the sites only have access to information fed through Chrome and are unable to move away from it.
It prevents malicious websites from taking control of others, in particular login information or other delicate data as websites can no longer talk to each other and share information via the web browser of your phone.
The side effects of this new behavior is that each website has its own sandbox, that ensures that they take a lot of room on the mobile if you can picture a bunch of real sandboxes in someone’s yard. This implies that the RAM use of Chrome is already meme-worthy, but is done for the sake of secure computing, it is a bit higher than in the past. As such, it is only usable on computers with more than 2 GB of RAM automatically.
If this functionality is familiar, it is already available for Chrome for Windows which requires all websites to use the functionality by default. This function is only automatically allowed on the mobile version of pages needing users to log in.