We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

Teema arhiveeriti. Please ask a new question if you need help.

Firefox crashes

  • 2 vastust
  • 1 on selline probleem
  • 23 views
  • Viimati vastas pawelk

pawelk
pawelk
more options

Crash ID: bp-ff9c5650-3bf1-4876-82fc-2c3a30190314 Starting Firefox, both in normal and safe mode, opens the Crash Reporter dialog.

Crash ID: bp-ff9c5650-3bf1-4876-82fc-2c3a30190314 Starting Firefox, both in normal and safe mode, opens the Crash Reporter dialog.

Valitud lahendus

Thank you for replying so quickly!

I have downloaded and unpacked Firefox Developer Edition 67.0.b1 archive (so, the same version number that's in the crash report) over the one that was crashing and it has solved the issue. This leads me to believe it might have been a borked auto-update.

Loe vastust kontekstis 👍 0

All Replies (2)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Hmm, I can't tell what causes this crash. It doesn't seem unique to beta/developer; it has been detected for several past versions. But everything was fine for you with Firefox 66?

pawelk
pawelk Küsimuse esitaja
more options

Valitud lahendus

Thank you for replying so quickly!

I have downloaded and unpacked Firefox Developer Edition 67.0.b1 archive (so, the same version number that's in the crash report) over the one that was crashing and it has solved the issue. This leads me to believe it might have been a borked auto-update.