Firefox opening but not working on Mac OS Sonoma
Categories
(Core :: IPC, defect)
Tracking
()
People
(Reporter: kolcon, Unassigned)
Details
Steps to reproduce:
- get firefox (any, ESR, 121.0.1, does not matter), install it on Sonoma
- launch it (with a clear profile to make sure addons don't interfere)
Actual results:
Firefox opens after a while but appears frozen.
After a while it loads, but you cannot open any page in it, it freezes for a couple of seconds each time you click something and is in general not usable.
In the terminal I can see these messages:
[Parent 2414, IPC Launch #2] WARNING: parent MachReceivePortSendRight failed: 0x10004003 (ipc/rcv) timed out: file /builds/worker/checkouts/gecko/ipc/glue/GeckoChildProcessHost.cpp:1366
[Parent 2414, IPC I/O Parent] WARNING: Failed to launch tab subprocess: file /builds/worker/checkouts/gecko/ipc/glue/GeckoChildProcessHost.cpp:787
Safari and Chrome run both OK on the machine.
The tips from other pages (disable ipv6, http3 in about:config, HW acceleration) do not help.
Expected results:
Firefox should be running smoothly.
|
||
Comment 1•2 years ago
|
||
I was not able to reproduce the issue on Mac 14.1 Sonoma using Firefox builds 121.0, 121.0.1 and 115.6.0esr with new profile, Firefox opened instantly.
Can you please add more details? Thank you.
I would love to, but I run out of ideas what to try.
I cannot even access about:config
I guess it may something to do with the subprocess creation that handles (new) tabs. But search did not provide any useful clues.
OK the problem went away when using boot arg: ipc_control_port_options=0
|
||
Comment 4•2 years ago
|
||
Not sure if this bug is still reproducible but moving to Core IPC for triage
|
||
Comment 5•2 years ago
|
||
The error being logged is caused when a content process, upon starting, is unable to check-in with the parent process within 10 seconds. Based on comment 3, it sounds like you may be running a customized macOS install with some startup options changed, perhaps which has caused the mach IPC messaging subsystem to start misbehaving?
I'm not sure if there's much we can do on the Firefox side to work around this issue. If this is reproducing on officially supported macOS hardware/software combinations, please re-open, and we can continue trying to investigate.
Description
•