
Firefox crashes at startup in macOS 10.13 (High Sierra) public beta 3
Since installing this build of High Sierra, Firefox 54.0.1 won't launch—not even in safe mode. (I also tried v55.0 beta. Same behavior.)
Chosen solution
FYI, as of the latest build of High Sierra, this issue seems to be resolved (with no changes to my Firefox configuration).
Read this answer in context 👍 0All Replies (13)
soundsgood said
Firefox 54.0.1 won't launch—not even in safe mode.
If you can't get Firefox to open, you will have to do this the hard way.
https://support.mozilla.org/en-US/kb/mozillacrashreporter Open the file browser / explorer on your computer. Note: You may have to enable Show Hidden Folders / Files. Enter this in the address bar;
Windows: %APPDATA%\Mozilla\Firefox\Crash Reports\submitted Win 7/Vista: C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Crash Reports\submitted Win XP/2000: C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Crash Reports\submitted
Mac OS: /Users/<username>/Library/Application Support/Firefox/Crash Reports/submitted Linux: /home/<username>/.mozilla/firefox/Crash Reports/submitted
Copy the most recent 5-7 File Names in the folder. Post the information in the reply box.
Beta versions do sometimes have problems. You should think about installing normal Firefox until the issue is fixed.
FredMcD said
soundsgood saidFirefox 54.0.1 won't launch—not even in safe mode.If you can't get Firefox to open, you will have to do this the hard way.
https://support.mozilla.org/en-US/kb/mozillacrashreporter Open the file browser / explorer on your computer. Note: You may have to enable Show Hidden Folders / Files. Enter this in the address bar;
Windows: %APPDATA%\Mozilla\Firefox\Crash Reports\submitted Win 7/Vista: C:\Users\<username>\AppData\Roaming\Mozilla\Firefox\Crash Reports\submitted Win XP/2000: C:\Documents and Settings\<username>\Application Data\Mozilla\Firefox\Crash Reports\submitted
Mac OS: /Users/<username>/Library/Application Support/Firefox/Crash Reports/submitted Linux: /home/<username>/.mozilla/firefox/Crash Reports/submitted
Copy the most recent 5-7 File Names in the folder. Post the information in the reply box.
Thanks. There are only three files in that folder, and one of them was created in January. So, here are the two from the last 24 hours:
bp-9600b6bf-1f9b-4663-8b93-099c01170716.txt
bp-c4b3ce39-362e-41c4-a790-ca2981170716
.txt
I believe that's what you asked for. If I misunderstood you, please let me know. Thanks again.
(It's interesting that while Firefox has actually crashed at least 7 times in the last 24 hours, there are only two, recent crash reports.)
FredMcD said
Beta versions do sometimes have problems. You should think about installing normal Firefox until the issue is fixed. Download Firefox For All languages And Systems {web link}
It seems you misunderstood my post. But thanks, anyway.
soundsgood said
FredMcD saidBeta versions do sometimes have problems. You should think about installing normal Firefox until the issue is fixed. Download Firefox For All languages And Systems {web link}It seems you misunderstood my post. But thanks, anyway.
Sorry. I hit send before finishing…
Your post seemed to imply that I run betas of Firefox all the time, but that's not the case.
I only installed the beta as a test to see if the issue might have been corrected in a newer version than the publicly released version I'd been running normally. It didn't. And I didn't keep the beta.
Thanks again.
soundsgood said
There are only three files in that folder, and one of them was created in January. So, here are the two from the last 24 hours:
Might be the other reports were not submitted.
Product Firefox Release Channel release Version 54.0.1 Build ID 20170628075643 OS OS X 10.13 OS Version 10.13.0 17A306f
bp-9600b6bf-1f9b-4663-8b93-099c01170716
bp-c4b3ce39-362e-41c4-a790-ca2981170716
Signature: AppleIntelHD5000GraphicsMTLDriver@0x2a9f7
This is for Sumo's Related Bugs 1381354 NEW --- Crash in AppleIntelBDWGraphicsMTLDriver@0x273d1 and many other signatures, all with crash address 0x20
This bug was just opened yesterday. Only Macs seem to be effected.
Several ideas to try out.
Start your Computer in safe mode. Then start Firefox. Try Safe websites. Is the problem still there?
http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia
See if there are updates for your graphics drivers https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration
Did the issue start when you started using FF v54? What about prior versions? Were there any problems?
FredMcD said
This bug was just opened yesterday. Only Macs seem to be effected.
Thanks. So, what does that mean? I'm new here, so I don't know what to expect. How will I know that it's been addressed?
A bug report was opened, so it is being addressed. How soon will this be fixed? Unknown.
FredMcD said
Did the issue start when you started using FF v54? What about prior versions? Were there any problems?
FredMcD said
Several ideas to try out. Start your Computer in safe mode. Then start Firefox. Try Safe websites. Is the problem still there? http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia
See if there are updates for your graphics drivers https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration
Did the issue start when you started using FF v54? What about prior versions? Were there any problems?
Sir, I appreciate your willingness to help, but respectfully, it seems you didn't actually read my initial post, because you're asking about things I already addressed there. :-)
Fred was asking you to put your computer into Safe Mode, not Firefox itself. However, I'm unsure if Macs have an alternative to Safe Mode like Windows does.
On the bug side, Mozilla QA has reproduced the issue on 10.13 Beta 3 so now we just wait for a fix.
I hope that you aren't using the High Sierra beta as your daily driver OS. Running a pre-release build of any OS as daily is risky.
Chosen Solution
FYI, as of the latest build of High Sierra, this issue seems to be resolved (with no changes to my Firefox configuration).
That was very good work. Well done. Please flag your last post as Solved Problem so others will know.