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

Firefox crashes

  • 1 odgovor
  • 1 ima ovaj problem
  • 11 views
  • Posljednji odgovor poslao philipp

more options

I have recently received a new work laptop, and I can't seem to get firefox to startup at all. I have uninstalled/re-installed with multiple different versions (40.0, 40.0.2, 40.0.3, 40.0.3-funnelcake43) and they all end up with an access violation exception when trying to start Firefox. It will not start in safe mode either, the same unhandled exception is thrown. I know it is the case of trying to read from memory address 0, but obviously I can't figure out what is missing in order to fix that.

Crash report id: bp-2be3e004-a093-4844-ab74-9617b2150915

(I sent a few before I unchecked the box).

I have recently received a new work laptop, and I can't seem to get firefox to startup at all. I have uninstalled/re-installed with multiple different versions (40.0, 40.0.2, 40.0.3, 40.0.3-funnelcake43) and they all end up with an access violation exception when trying to start Firefox. It will not start in safe mode either, the same unhandled exception is thrown. I know it is the case of trying to read from memory address 0, but obviously I can't figure out what is missing in order to fix that. Crash report id: bp-2be3e004-a093-4844-ab74-9617b2150915 (I sent a few before I unchecked the box).

All Replies (1)

more options

hi, thanks for providing a crash id - this is an issue on devices running websense endpoint security software. apparently they are working on a fix to be release soon - for details and/or progress on this issue you can also follow along in bug #1181091, where this issue is tracked.