Closed Bug 1926385 Opened 4 months ago Closed 4 months ago

Starting nightly with profile fails

Categories

(Core :: IPC, defect)

Firefox 133
defect

Tracking

()

RESOLVED DUPLICATE of bug 1925774

People

(Reporter: mozilla, Unassigned)

References

Details

Steps to reproduce:

I update nightly manually from the tar.bz2 every day. I then start nightly from the command line using
$ /usr/local/bin/firefox --new-instance --ProfileManager

Actual results:

Whenever I start nightly, the first invocation always fails. Sometime the failure looks like this, if it is the first try after the update of nightly.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 8025, IPC I/O Parent] WARNING: process 8081 exited on signal 9: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:335
After the first invocation of nightly, if I shut it down and start it again, it looks like this:
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
It always works if I run the command again.
The other difference is that before this started happening, there was only 2 of the
ATTENTION: default value of option mesa_glthread overridden by environment.
responses, instead of 3.

Expected results:

A successful invocation of nightly now looks like this,
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.

Before it started happening it looked like this,
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
or if it was the first invocation after an update, like this,
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 8025, IPC I/O Parent] WARNING: process 8081 exited on signal 9: file /builds/worker/checkouts/gecko/ipc/chromium/src/base/process_util_posix.cc:335
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.

This is a pretty obscure error, and there is a simple workaround, just running the command again, so I don't really expect a fix, I am just posting this so there is a record of the issue in case a developer is fixing something related. I can't use mozregression to find the offending update to nightly, so it would be a real bear to bisect this.

The Bugbug bot thinks this bug should belong to the 'Core::IPC' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → IPC
Product: Firefox → Core

This sounds very similar to bug 1925774, which is now fixed in Nightly. Can you wait for a day and check again?

See Also: → 1925774

Yes, this seems to have resolved the issue, as I don't see it in the latest nightly. When I looked for existing bugs, I must not have used the proper search terms, because that bug didn't show up. Or maybe it was already closed, and it was a timing issue. Thanks for your response.

Status: UNCONFIRMED → RESOLVED
Closed: 4 months ago
Resolution: --- → WORKSFORME
Duplicate of bug: 1925774
Resolution: WORKSFORME → DUPLICATE

Thanks for testing and reporting bugs!

You need to log in before you can comment on or make changes to this bug.