User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

With Firefox 68.0b3:
Open a Firefox windows with default profile.
From a terminal run ./firefox -P another_profile
(or ./firefox --ProfileManager or ./firefox --profile <path-to-profile> )

Actual results:

A new tab is opened in the first window (with default profile)

Expected results:

A new window is opened with "another_profile"

Since bug 469990 you will need to pass --no-remote in order to open a new instance of Firefox.

Yuri, would you like to take a look at this?

Adding a voice.

FIrefox 68.0 (64-bit)
macOS Mojave 10.14.5

Running the following command used to spawn a new Firefox instance (in it’s own window) of my development profile.

alias firefox_dev="bash -c 'nohup /Applications/Firefox.app/Contents/MacOS/firefox-bin -p development > /dev/null 2>&1 &'"

Now, it opens a new window of my default profile.

As suggested by Dave, adding --no-remote fixes the issue, but unsure if it’s a monkey patch or expected behavior.

(In reply to Stephen A Pohl [:spohl] from comment #2)

Yuri, would you like to take a look at this?

Looking into these.
Not clearing the NI to keep track of them.

Should be handled in https://bugzilla.mozilla.org/show_bug.cgi?id=1565597

I don't think there is value in an additional bug here. We can reopen this if bug 1565597 doesn't fix this.