Join the Mozilla’s Test Days event from 9–15 Jan to test the new Firefox address bar on Firefox Beta 135 and get a chance to win Mozilla swag vouchers! 🎁

Mozilla 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 in safe mode

  • 5 प्रत्युत्तर
  • 4
  • 4 views
  • के द्वारा अंतिम प्रतियुतर Volleyjosh

more options

Firefox updated to a new version (firefox.exe is 16.0.2, but dated 11/12/2012, today is 11/29/2012) and now crashes in normal,safe and -profile mode. I have many crash dump ID's, i've put the most recent two into the Troubleshooting information.

Firefox updated to a new version (firefox.exe is 16.0.2, but dated 11/12/2012, today is 11/29/2012) and now crashes in normal,safe and -profile mode. I have many crash dump ID's, i've put the most recent two into the Troubleshooting information.

Volleyjosh द्वारा सम्पादित

चुने गए समाधान

Update Firefox to 17.0.1 (releasing later today) Update Firefox to the latest release

Then try to retest.

संदर्भ में यह जवाब पढ़ें 👍 2

All Replies (5)

more options

चयनित समाधान

Update Firefox to 17.0.1 (releasing later today) Update Firefox to the latest release

Then try to retest.

more options

Disable hardware acceleration.... Intructions here: https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration

Bug info here: https://bugzilla.mozilla.org/show_bug.cgi?id=700840 <p> From that page: "The user disabled the Hardware Acceleration in Firefox and the issue seemed to be gone. His computer has Nvidia SLI technology (Q6600, Win 7 x64 and SLI of GTX460), surely the culprit..."

more options

That bug is totally different than the crash ID's the user gave. Disabling Hardware Acceleration may be useful, but that bug report is wrong.

more options

Ofcourse the crash ID is different What do you mean the bug report is wrong? Same crash reason, same operating system.

more options

Newest version fixed the issue. Thanks!