Firefox Developer Edition 91.0b9 crashes, crash reporter not working. MacOS 10.15.7.
Firefox started crashing a few times a day after updating to v91.
Crashed Thread: 5 Socket Thread
Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information: stack buffer overflow
I checked and It looks like crash reports aren't being sent to Mozilla, even though it's enabled in settings. The last one that was sent was in 2019.
When I try to open "Firefox Developer Edition Crash Reporter.app", the crash reporter crashes.
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x1] Library missing
Application Specific Information: dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/libnss3.dylib Referenced from: /private/var/folders/*/crashreporter.app/Contents/MacOS/crashreporter Reason: image not found
Toate răspunsurile (3)
Start Firefox using Troubleshoot(Safe) Mode {web link}
A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?
While still in Troubleshoot(Safe) Mode,
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.
Please, Do not post a screenshot ! !
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
Try to do a clean reinstall and drag the current application to the Trash.
You can create a new profile as a quick test to see if your current profile is causing the problem.
See "Creating a profile":
If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.
Modificat în de cor-el
FredMcD said
Start Firefox using Troubleshoot(Safe) Mode {web link} A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there? While still in Troubleshoot(Safe) Mode, In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them. The crash report is several pages of data. We need the report numbers to see the whole report. Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in. Please, Do not post a screenshot ! !For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
I started up in safe mode and went to about:crashes. it just says "No crash reports have been submitted."
I can see lots of crash logs in console.app though.
