containers for Firefox

[Casper31 73]

Firefox has a new promising plugin called :Firefox Multi-Account Containers

Mozilla developed the plug to enhance Privacy.

I installed it today,but if you use it for a longer time,let me know what you think.

 

https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/

https://www.youtube.com/watch%3Fv=Gy7lyvAfOSw

 

Gr,Casper

[OpenSourcerer 1359]

From my personal point of view, having multiple profiles is safer. One is for work, one is for private, one is for experiments. Work/Private is obvious, Experiments profile will allow you to change settings and install addons for testing before being propagated to the other profiles. If Experiments breaks, restore from backup or simply reverse the changes if possible.

firefox -P

will launch a profile manager which allows you to choose which profile you would like to use.

[De Facto Pantalones 12]

I've been playing w/ Containers since Quantum's release.  It's a neat feature for sure... now I've taken the time to realize it's function/utility benefits. 

 

Quick question... does using various container tabs use more or less RAM?  I've looked at my Resource Monitor from time to time (4 processes enabled on my machines)... and I see increased RAM (slight, but nonetheless).  I don't understand why the need for more RAM via Containers, versus an open tab in current browser.  Any feedback would be great... but main topic, Containers are pretty cool.  I dig them.  Thanks!

[OmniNegro 155]

If I understand it at all, every container uses a separate process and its own RAM. Some parts are likely shared between processes, but when you do something in a container that changes it in any way, that has to be kept separate. So for instance if you wanted to install "Cookie Autodelete" and made a container to test it, that container could possibly crash, since this is a new extension on that container. (Unlikely in this example, but imagine other extensions.) When a container is crashing, because it is using a different process to hold the data that may have led to the crash, nothing else is lost. So the main Firefox process just shrugs and moves on.

 

It is this separation that makes it use more RAM. But not a huge amount.