Open Bug 2011806 Opened 1 month ago Updated 7 days ago

macOS GPU process fails to launch on artifact builds

Categories

(Firefox Build System :: General, defect, P1)

defect

Tracking

(firefox-esr115 unaffected, firefox-esr140 wontfix, firefox147 wontfix, firefox148 wontfix, firefox149 fix-optional)

Tracking Status
firefox-esr115 --- unaffected
firefox-esr140 --- wontfix
firefox147 --- wontfix
firefox148 --- wontfix
firefox149 --- fix-optional

People

(Reporter: haik, Assigned: haik)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

On macOS artifact builds, the new GPU process fails to launch causing fallback to software webrender. This has the same root cause as bug 1950310 where the artifact binary branding doesn't match the repo branding.

$ ./mach run
[Parent 46284, IPC I/O Parent] WARNING: Failed to launch gpu subprocess @posix_spawnp (Error:0): file /builds/worker/checkouts/gecko/ipc/glue/GeckoChildProcessHost.cpp:825
[Parent 46284, IPC I/O Parent] WARNING: Failed to launch gpu subprocess @posix_spawnp (Error:0): file /builds/worker/checkouts/gecko/ipc/glue/GeckoChildProcessHost.cpp:825
[Parent 46284, IPC I/O Parent] WARNING: Failed to launch gpu subprocess @posix_spawnp (Error:0): file /builds/worker/checkouts/gecko/ipc/glue/GeckoChildProcessHost.cpp:825
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Fallback WR to SW-WR (t=0.715832) [GFX1-]: Fallback WR to SW-WR
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Fallback WR to SW-WR (t=0.715832) |[1][GFX1-]: Failed to launch GPU process after 3 attempts (t=0.715855) [GFX1-]: Failed to launch GPU process after 3 attempts
No longer blocks: artifact, 1785390
No longer depends on: 1950310

Set release status flags based on info from the regressing bug 1827747

Summary: macOS GPU process fails to launch on articact builds → macOS GPU process fails to launch on artifact builds

A workaround for now to at least have a GPU process with artifact builds on macOS is to set layers.gpu-process-executable.enabled to false.

Another workaround for mozilla-central artifact builds is to use official nightly branding in your mozconfig.

ac_add_options --enable-artifact-builds
ac_add_options --with-branding=browser/branding/nightly

The severity field is not set for this bug.
:ahochheiden, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(ahochheiden)

This doesn't affect users, but is important to fix for developers testing Firefox using artifact builds. I'm working on a fix.

Severity: -- → S3
Flags: needinfo?(ahochheiden)

Hi Haik. I want to ask if you may have an update for this bug. Thanks!

(In reply to Henrik Skupin [:whimboo][⌚️UTC+1] from comment #7)

Hi Haik. I want to ask if you may have an update for this bug. Thanks!

No progress to report right now. I have a WIP patch and hope to get it posted for review within the next 1 to 2 weeks. Sorry for the delay.

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