Andreas Tolfsen ❲:ato❳ Reporter
	Description • 6 years ago

If Firefox has a pending upgrade, it will start the Firefox process,
detect there’s an update, quit Firefox, start the updater program,
and then restart Firefox.

This creates problems for geckodriver because it detects this as
if the Firefox process ended (which it technically did):

> curl -d '{}' http://localhost:4444/session
> {"value":{"error":"unknown error","message":"Process unexpectedly closed with status 0","stacktrace":""}}

I would propose that we find which preference controls this, and
set this from geckodriver before starting Firefox so that users are
not surprised by an upgrade lurking.  An alternate solution would
be to prevent Firefox from upgrading tself when started with the
-marionette flag, but this may inhibit writing upgrade tests.

	Henrik Skupin [:whimboo][⌚️UTC+1]
	Comment 1 • 6 years ago

The problem here is bug 1112937, which causes indeed problems when an update has been downloaded by a different profile. I don't know if there is anything we can actually do to help in such a situation except telling the users to finish the update first. But maybe there is a solution. So lets ask Rob if he knows or has an idea.

Andreas, I wonder how Marionette handles that behavior. Maybe it's a geckodriver issue only?

	Andreas Tolfsen ❲:ato❳ Reporter
	Comment 2 • 6 years ago

We probably can’t fix this because the updater process replaces
Firefox, causing geckodriver to error on the process unexpectedly
exiting.