Firefox crashes on start #21
Comments
|
Could you please provide some more information about the build you used? Was it 133a01 or 132.0, and if so, did you definitely download the build within the past week? I ask because we thought we fixed this, and because the developer periodically uploads new builds that don't change the release version (because it follows the upstream version). Are you seeing a freeze (beachball) or an actual crash? Is there any kind of backtrace? Can you provide any other information about your system? We're going to need some more information! |
|
I used |
Where is this one? |
...no I'd think it would still read the profile regardless of where the browser was started from, unless this is some new security thing on modern macOS (modern relative to what I run) that I don't know about? Releases are all at https://github.com/i3roly/firefox-dynasty/releases. |
|
I found the newest one, but when I click on latest release it is not there |
|
133.a01 crashes too |
|
Can you please post a backtrace? |
I even uninstalled the ESR profile |
|
|
Yeah, that's a real crash, not the freeze we were seeing previously. The log you posted isn't a backtrace. I guess the OS isn't giving you a backtrace? That's... annoying. Okay, thanks for answering my questions, although I'm out of ideas for the moment... |
|
Oh! Here's what might tell us more—can you please launch the Firefox binary directly and tell us if the Terminal prints anything? (Run |
|
No verbosity from terminal and same crash. |
|
I wonder if this |
Correct, you can ignore it. |
|
|
https://developer.apple.com/forums/thread/706442 |
|
Hmm, does anything change if you run |
|
No, same |
|
|
that just seems like the exception handler itself crashed when trying to write out the minidump file. Still shouldn't happen though, but newer osx has wacky code sign restrictions and stuff. |
|
On Tuesday November 19 2024 04:46:46 Crosmatron wrote:
This is what worked for me:
`codesign --remove-signature Firefox.app`
In that case, you could try to re-sign a fresh copy taken from the .zip file:
```
codesign -f --verbose --deep --preserve-metadata --sign - Firefox.app
```
If that command fails you can try again without the `--preserve-metadata` argument.
If you have a code signing certificate of your own you can use that instead of the default identity (`-`) of course.
The idea is to replace the existing signature (that's considered invalid, for whatever reason) with one that's made on your own system and should thus have more chance to comply with the "local rules".
But of course there is no need to sign the application if it everything works as it should for you. The only "risk" is probably that you'll have to grant certain permissions repeatedly (like for accessing or being accessed from the internet).
|
|
I don't know if this will solve your issue, but I noticed that Firefox Dynasty would crash on launch if there were older preference files lurking. I used AppTrap to clear everything, and on a fresh install Dynasty didn't crash. |
I used AppCleaner Uninstaller to remove all Firefox related so that did not help. |
|
i'm closing this because i can't reproduce it, nor can anyone else. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
macOS 10.14.6:
The text was updated successfully, but these errors were encountered: