Chrome is a Google Service that happens to include a Browser Engine

Re:Chrome is a Google Service that happens to include a Brow... by TheDong on Saturday September 22, 2018 @10:17PM (#18049039)

> Firefox has a concept of profiles but AFAICT you can only run one profile at a time. :(

You can have one primary firefox instance, and any number of instances that have the "--no-remote" flag set, each running different profiles. Any links you click outside of firefox (e.g. xdg-open) will use the primary firefox.

The 'firefox --no-remote -P' trick has worked for longer than chrome has existed and I've been using it to juggle about 15 profiles since firefox 3, usually having 4 different firefox instances open with 4 different profiles.

The more user-friendly way to do this is with firefox containers though.

[ Parent | on HN ]

Re:Chrome is a Google Service that happens to include a Brow... by pastununtrium on Sunday September 23, 2018 @03:51AM (#18049936)

What is the memory hit though. Do the separate profile processes share some of the library memory or do they each reuse a lot of memory. I’d assume chrome profiles being natively supported via a easy GUI means the separate profile processes are able to share memory??

[ Parent | on HN ]