Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Firefox crashes

  • 1 përgjigje
  • 1 e ka hasur këtë problem
  • 1 parje
  • Përgjigjja më e re nga 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).

Krejt Përgjigjet (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.