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.

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.

Learn More

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Firefox crashes

  • 5 fhreagra
  • 2 leis an bhfadhb seo
  • 5 views
  • Freagra is déanaí ó cor-el

more options

Multiple crashes on startup; have installed new copies of Firefox, checked permissions with disk utility, assured that Mac OS is up to date, tried safe mode (still occurs), running iMac with OS X 10.5.8

Multiple crashes on startup; have installed new copies of Firefox, checked permissions with disk utility, assured that Mac OS is up to date, tried safe mode (still occurs), running iMac with OS X 10.5.8

Réiteach roghnaithe

Such bug fixes only land on the trunk (mozilla-central), so you would have to try the latest Nightly build with a fresh profile to see if you still get that error.

Read this answer in context 👍 0

All Replies (5)

more options

Please open firefox and in the address bar type about:crashes then hit enter. Please copy and paste the top result to this thread.

Athraithe ag Tom Farrow ar

more options

bp-982562a7-a846-4a46-a0f4-86a712120109

more options

The bug has been reopened, see https://bugzilla.mozilla.org/show_bug.cgi?id=702217 Wait for a fix.

more options

Don't know if anything has been done on your end, but the bug SEEMS to be fixed, or at least ineffective. Might have something to do with a reboot, occasioned by several Microsoft crashes (Word, PPT). At any rate, Firefox seems to be happily rolling along. Thanks for your attention!

more options

Réiteach Roghnaithe

Such bug fixes only land on the trunk (mozilla-central), so you would have to try the latest Nightly build with a fresh profile to see if you still get that error.