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!

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.

Learn More

This thread was archived. اگر به کمک نیاز دارید لطفاً یک سؤال بپرسید.

Firefox crashes

  • 1 پاسخ
  • 1 has this problem
  • 1 view
  • آخرین پاسخ توسّط philipp

desktopsupport
desktopsupport
more options

Upon trying to start up Firefox 40.0, 40.0.2, or 40.0.3, it shows the main window for approximately two seconds and then crashes, showing the crash reporter. It crashes in safe mode the same way. The crash report shows: Crash ID: bp-7bbba0b3-7e95-4e8b-98f4-a4db02150828

Clean uninstalls and reinstalls of any version of 40 does not help. This affects all Windows PCs in our organization, they all have the same issue. Version 39.0.3 and earlier work without issue.

Upon trying to start up Firefox 40.0, 40.0.2, or 40.0.3, it shows the main window for approximately two seconds and then crashes, showing the crash reporter. It crashes in safe mode the same way. The crash report shows: Crash ID: bp-7bbba0b3-7e95-4e8b-98f4-a4db02150828 Clean uninstalls and reinstalls of any version of 40 does not help. This affects all Windows PCs in our organization, they all have the same issue. Version 39.0.3 and earlier work without issue.

All Replies (1)

philipp
philipp
  • Moderator
more options

hi, unfortunately this seems to be an issue with websense endpoint on those devices interfering. for more background on this you can also go through the comments in bug 1181091.