Re:Adware vendors buy Chrome Extensions to send ad- and malw...
by riquito on Saturday January 18, 2014 @03:09PM
(#7082062)
To run a new, separated Firefox with a (possibly) different profile
It's always handy to have a "vanilla" profile, to compare how much the extensions tuned down the browser or try to understand if the error that you're seeing is caused by an extension. Having a "privacy" profile with some ad-hoc extensions helps too.
[ Parent
| on HN ]
Re:Adware vendors buy Chrome Extensions to send ad- and malw...
by Steuard on Saturday January 18, 2014 @09:42PM
(#7083171)
Mind you, -ProfileManager actually opens to the full profile manager interface (where you select a profile to run, or create a new one, or whatever). You can load a specific profile (that already exists) directly by replacing "-ProfileManager" with "-P [profile name]". (Omitting the name will open the manager, too.)
https://developer.mozilla.org/en-US/docs/Mozilla/Command_Lin...
Re:Adware vendors buy Chrome Extensions to send ad- and malw...
by pasbesoin on Sunday January 19, 2014 @02:35AM
(#7083755)
Ah, I guess that's why I remembered -p -- or -P, as the case may be.
Re:Adware vendors buy Chrome Extensions to send ad- and malw...
by pasbesoin on Saturday January 18, 2014 @03:53PM
(#7082204)
Thanks. Sorry I mis-remembered the flag(s) from memory. And be sure you're using both, to make sure the separate profiles do not share the same process or something like that (again, from memory; Google can quickly turn up the details).
Re:Adware vendors buy Chrome Extensions to send ad- and malw...
by riquito on Saturday January 18, 2014 @04:24PM
(#7082289)
Your memory is right. Without -no-remote you would end up spawning another windows from the currently running firefox. Without -ProfileManager you can't choose a different profile.
It's also a good idea to use different themes per profile (and I see you suggested it too).