Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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.

Learn More

Este fío arquivouse. Faga unha nova pregunta se precisa axuda.

Firefox crashes on startup

  • 2 respostas
  • 1 has this problem
  • 4 views
  • Last reply by Keslaa

Keslaa
Keslaa
more options

This is happening to many computers on our network and started this morning. If Firefox was open overnight, then it continues to work fine. Closing and reopening FF causes the crash notification to appear. I am unable to start FF in it's safe mode.

Crash ID: bp-efa5c800-80ef-4852-a1c8-f57302160913

This is happening to many computers on our network and started this morning. If Firefox was open overnight, then it continues to work fine. Closing and reopening FF causes the crash notification to appear. I am unable to start FF in it's safe mode. Crash ID: bp-efa5c800-80ef-4852-a1c8-f57302160913

Chosen solution

After seeing your response, I tested and have confirmed that Symantec does seem to be the issue. Thank you for getting me started in the right direction.

Ler a resposta no contexto 👍 0

All Replies (2)

philipp
philipp
  • Moderator
more options

hi Keslaa, thanks for providing a crash report id. we have seen quite a number of similar reports about this issue in the last hours and this issue is likely caused by your symantec security software that is hooking into firefox (probably through a program/signature update done by them). other users reported that updating firefox in this situation helped with the crashes. you can download & install the latest firefox from https://www.mozilla.org/en-US/firefox/all/

Keslaa
Keslaa Question owner
more options

Chosen Solution

After seeing your response, I tested and have confirmed that Symantec does seem to be the issue. Thank you for getting me started in the right direction.