Immediatly force closes on mojave

[Jghauri05]

Works perfect on High Sierra but immediately force closes on Mojave. no matter which version

[AuroraMartell]

Works perfect on High Sierra but immediately force closes on Mojave. no matter which version

I'm also experiencing this.

[RJVB]

AuroraMartell left a comment (i3roly/firefox-dynasty#67) > Works perfect on High Sierra but immediately force closes on Mojave. no matter which version I'm also experiencing this.

Could this be another case of the OS somehow not accepting how the bundle has been signed, and that might be solved by re-signing locally?

[Wowfunhappy]

What happens if you start the Firefox binary directly via the Terminal?

[gabriferrari93]

Hello!

What happens if you start the Firefox binary directly via the Terminal?

Yes, it crashes also via terminal for me too on Mojave. Here the report of the crash, as RJVB was saying, it seems some sort of invalid signature.

firefox_mojave_crash.txt

[Wowfunhappy]

@gabriferrari93 What happens if you option-click Firefox.app and select "open"?

If that doesn't work, can you please try completely disabling gatekeeper? Run in Terminal:

sudo spctl --master-disable

You can change disable to enable to turn it back on afterwards.

[gabriferrari93]

@Wowfunhappy,

the app crashes also diabling Gatekeeper, with sudo spctl --master-disable, and gives the same crash:

Crashed Thread: 4 Breakpad ExceptionHandler
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

both with the GUI way selecting "open" and via terminal. BUT, executing the removal of the signing with

sudo codesign --remove-signature /Applications/Firefox.app
i am now able to open the app.

The problem now was that every tab crashes into firefox with the message "Gah. Your tab just crashed.".
Trying around with Claude AI, two causes emerged:

• plugin container crashes due to wrong library paths
• again codesign problem on plugin container.
  Claude has generated a recap of these at this link: https://claude.ai/public/artifacts/7d4794ea-dd39-4dd2-bb9e-277d39210974

And now Firefox is up and running flawlessly on Mojave! :)

[Wowfunhappy]

...I'm still not sure what's going on with the code signature but I'm glad --remove-signature worked and now I'll know the next time someone has this problem! I'm still not sure what is actually going on, does JIT really need a special entitlement on Mojave?

[gabriferrari93]

Good question, I have to verify. From what Claude have said: "with macOS 10.14 Apple introduced Hardened Runtime which blocks write+execute memory allocation by default. Firefox needs this for:
• JavaScript JIT compilation
• WebAssembly execution
• Dynamic code generation"

Appears that from Mojave, the entitlement com.apple.security.cs.allow-jit is ignored if the binary is not signed with a trusted certificate.

Would be nice knowing if these crashes happen also in high versions of macOS. I can test it on Catalina and Monterey in the incoming days. I will you update on this ;)