Restarting a non-default profiles doesn't work

[hannahmontana]

Steps to reproduce:

• Create a new profile from about:profiles

• In the new profile either install a new non-bootstrapped addon and press restart, or just choose the 'restart' option from the menu

• Observe the window close and a new window of the default profile pop up

[Moonchild]

If you do not use the normal on-startup profile manager and keep the default setting (automatically start with the default profile) then any restart of the browser will automatically start your browser with the default profile. That works exactly as it should.
If you want to actively use multiple profiles, start the browser with -profilemanager and uncheck "use the selected profile without asking on startup"

[ron_1]

Moonchild wrote:
If you want to actively use multiple profiles, start the browser with -profilemanager and uncheck "use the selected profile without asking on startup"

Maybe I'm misunderstanding what's going on here, but when I performed the OP's "steps to reproduce" it restarted on the same non-default profile, even though I have "use the selected profile without asking on startup" checked.

EDIT
Okay, I just discovered something. If you have two browser windows open, one with the default profile, and the other with a non-default profile, when clicking Restart in the non-default profile, it will indeed restart with the default profile just like the OP states (then you'll have two browser windows opens, both with the default profile). If you have only one instance of the browser running with a non-default profile and click Restart, it restarts with the same non-default profile.

[Moonchild]

I'm sorry if I didn't understand the entire situation here. I didn't mean to add to confusion.

If you have 2 browser windows open with different profiles, then at least one (the non-default, I'm guessing) will be running in no-remote mode. (if you have opened that with the button from about:profiles it will indeed be running in no-remote mode).
When hitting restart, the remote-enabled instance of the browser will open a new window in the already-opened (default) profile and you're NOT having 2 different instances anymore in that case, but instead just opened a new window in the running session. This is because the launch command sees the browser is already open and will in that case not launch another copy (that's by design).

All of this is correct behavior although potentially confusing if you don't know what's going on.

[therube]

Off-topic:
IMHO...
A restart of a browser, from within any particular Profile, however initiated, should always reopen the same Profile, regardless of anything else.

[Moonchild]

IMHO...
A restart of a browser, from within any particular Profile, however initiated, should always reopen the same Profile, regardless of anything else.

It does.

Only in the edge case where you are already running a different copy that is integrated in the OS it does not. There is no easy way around this without breaking other behavior that you want (e.g. not opening a new browser for every clicked link)