Please update to 57.0.2 as the fix is in the update https://support.mozilla.org/en-US/kb/update-firefox-latest-version

To check : Go to the Firefox 3 Bar Menu --> Help ? --> Troubleshooting Information Page and take a look in the Accessibility section if accessibility is set to "true" there. If yes, go to the Firefox 3 Bar Menu --> Options --> Privacy & Security panel and under Permissions check the setting to Prevent Accessibility Services from accessing your browser. Restart Firefox

If still issues with 57+ : You could try this please : Go the Menu then Tools --> Options --> Performance and untick everything. change the recommended size lower then see how it runs. Note: 0 = No Multi-processor = slow again. TRY 2 Restart Firefox after making these changes please.

No idea on the 52.5.0 Please supply more information.

Please let us know if this solved your issue or if need further assistance.

I did all that, switched to 57.0.2, made all the performance changes you suggested as well as the privacy/security changes. Still get the same "Gah" crash error.

I still can't copy any diagnostic info. The only thing I can capture is the crash report number, see below, but I can't open these reports as the browser crashes then.

Report ID Date Crashed CE91C646-5444-47CA-A8B9-535109347795 10/12/2017 13:04 61DCDFD5-2BDB-4A49-9589-936C7418A8AA 10/12/2017 13:03 1312D518-E71B-4705-820A-6D194D247A09 10/12/2017 13:03 A88D5C62-D430-435D-A118-4CA2B78F6D23 10/12/2017 13:03 1AE181A6-CFEF-4FCC-90D7-7114125F6A91 10/12/2017 13:03

Please send the crash reports as a bp- file URL as per instructions : https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support Only need last 3.

Thanks for trying to help. I appreciate it!

I could not access diagnostic info, as the browser crashes when I try to open a crash report in a new tab. I copied the info from the saved files as below, but each text file only contains one thing: The name of the bp file, nothing else. See below:

bp-98a9daba-313a-4d42-ae14-fd71e0171210 bp-f8d9b803-8028-43a9-931e-49a8b0171210 bp-17c0159f-e2f5-4a47-bd47-643f10171210 bp-e8e9b396-cc32-4a40-9133-074590171210 bp-494b2986-43fe-43fc-b3c5-dde600171210

Crash Reason : EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Shows mostly errors in Plugins, few in Firefox.

Please : https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer and https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles then https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings TEST....... If no issues then Extensions which need to be added back in 1 at a time and test .....

Please do the below. Extensions/addons are in your Profile. https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer

https://support.mozilla.org/en-US/kb/profiles-where-firefox-stores-user-data

Or it is your Profile : Make a new one and test ...: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Note: Any customization will revert back to default, you will also maybe need to reinstall Extensions.

Please let us know if this solved your issue or if need further assistance.

This bug report is linked:

• bug 1419004 - Crash in @0x0 | mozilla::plugins::PluginUtilsOSX::SetProcessName

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)

Thanks for the replies. I took some time to go to Apple, and we determined that the problem is definitely tied to the High Sierra update. Version 13.2 is not only preventing Firefox from connecting, but also Safari (strangely Chrome is working fine), as well as iTunes and the App store. They ran a cloud version of the old version of MacOS (10.12 instead of 13.2), and Firefox and Safari work fine with that.

So, cor-el's bug report makes sense, as well as the bug fix, but that seems above my pay grade: Do you mean that I would have to edit code inside of the Firefox app to fix this bug, or is there going to be a new Firefox release with that bug fix?

At any rate, I appreciate how you all are trying to fix it. It's what makes this project so successful. Thanks.

Beyond my pay grade...lol Volunteer...

Sorry, I get the gist of it but again I do Windows : I'm able to manually patch `Firefox.app/Contents/MacOS/XUL` by replacing the string "com.apple.LaunchServices" by "xom.apple.LaunchServices" as a workaround.

No idea about the above from the bug URL.

No idea when a release will happen Volunteer Support are not told it is a "surprise". Make could put out a patch also as it seems it is there issue and not FF's.

Suggest hounding them on it also.

Keep checking for a Update : https://support.mozilla.org/en-US/kb/update-firefox-latest-version

Do a uninstall then delete all Firefox Folders except your Profile (alpha numerical folder in a folder) then try to install as that is what we suggest.

No idea why will not run ESR https://www.mozilla.org/en-US/firefox/organizations/all/ Note : Legacy Extensions will be deleted or removed in any version update after May 2018.

Please let us know if this solved your issue or if need further assistance.