Closed Bug 1386727 Opened 9 years ago Closed 8 years ago

Crash during creation of firefox headless browser

Categories

(Firefox :: Headless, defect)

55 Branch
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jagannathante, Unassigned)

Details

(Keywords: crash)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 Build ID: 20170731163142 Steps to reproduce: Start firefox 55.0 with --headless flag Actual results: With no active session: > *** You are running in headless mode. > (firefox:27959): Gdk-CRITICAL **: gdk_x11_display_get_xdisplay: assertion 'GDK_IS_DISPLAY (display)' failed > ExceptionHandler::GenerateDump cloned child 28004 > ExceptionHandler::SendContinueSignalToChild sent continue signal to child > ExceptionHandler::WaitForContinueSignal waiting for continue signal... > exit 11 With another window running: > *** You are running in headless mode. > Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. Expected results: Headless session should be started.
Component: Untriaged → Widget: Gtk
Keywords: crash
Product: Firefox → Core
Component: Widget: Gtk → Headless
Product: Core → Firefox
It looks like you already have Firefox open and headless is trying to connect to that instance. To use another session, use the command line switches: --profile <some profile dir> --no-remote. <some profile dir> can be an empty folder. FWIW, we are discussing making --headless always default to a new empty profile.
I missed on the part "With no active session," however, try using an empty profile like I mentioned above for this as well.
I tried it with "firefox --headless --profile /tmp/headless --no-remote". The console just says: > *** You are running in headless mode. and no errors are printed.
(In reply to Jagan from comment #3) > I tried it with "firefox --headless --profile /tmp/headless --no-remote". > The console just says: > > *** You are running in headless mode. > and no errors are printed. That's the expected behavior. You then need to use something like marionettte to control the browser.
Closing in favor of bug 1401024.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.