All users were logged out of Bugzilla on October 13th, 2018
From bug 369147 comment 23. This is Mac OS X only. Steps to reproduce (in Terminal.app): 1. $ rm -rf /path/to/test-profile $ mkdir /path/to/test-profile 2. $ /path/to/Minefield.app/Contents/MacOS/firefox-bin -no-remote -profile /path/to/test-profile -foreground (Quit) 3. $ /path/to/Minefield.app/Contents/MacOS/firefox-bin -no-remote -profile /path/to/test-profile -foreground Actual results: During step (2) in the Error Console: Error: Warning: unrecognized command line flag -foreground Source File: file:///....app/Contents/MacOS/components/nsBrowserContentHandler.js Line: 747 ps -ef | grep firefox shows firefox started with two foreground flags: firefox-bin -no-remote -profile /path/to/test-profile -foreground -foreground Expected results: no "-foreground"-related error in the Error Console. Note: the "-foreground" flag in the steps to reproduce is needed to make sure Firefox starts in foreground, since it usually doesn't do that when launched from the terminal. The issue itself does *not* depend on the -foreground flag being passed initially. You may see this problem when using Firefox normally (usually after extension-related changes or upgrades).
I meant to say that during step 3 (i.e. second launch with the profile) the error does not occur and the difference between the two runs is that in step 2 Firefox restarts (and adds two -foreground flags to the child process command line) and in step 3 it doesn't do that.
You need to log in before you can comment on or make changes to this bug.