為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox 56 crashes at strtup

  • 3 回覆
  • 1 有這個問題
  • 2 次檢視
  • 最近回覆由 philipp

more options

Crash report - Crash ID: bp-77bd6068-2c51-4d88-9b36-6f76c1171022

Firefox 56 hung - program not responding Quit program Tried to restart no response to restart Tried to restart system upon restart of firefox after reboot of system got message firefox updating will restart shortly???? when it restarted got Mozilla Crash Reporter screen tried to start firefox in safe mode still get crash reporter screen uninstalled Firefox reinstalled fresh copy of firefox still get Crash Reporter screen firefox won't come up - help what do I do next?????

Crash report - Crash ID: bp-77bd6068-2c51-4d88-9b36-6f76c1171022 Firefox 56 hung - program not responding Quit program Tried to restart no response to restart Tried to restart system upon restart of firefox after reboot of system got message firefox updating will restart shortly???? when it restarted got Mozilla Crash Reporter screen tried to start firefox in safe mode still get crash reporter screen uninstalled Firefox reinstalled fresh copy of firefox still get Crash Reporter screen firefox won't come up - help what do I do next?????

所有回覆 (3)

more options

hi, you're running kaspersky and malwarebytes anti-exploit at the same time - this can lead to unforseen problems.

more options

Thank you for your quick response. I am running Kaspersky and Malwarebytes. I turned off exploit protection and was able to bring firefox up, BUT how do not loose that vunerability. Malwarebytes is upset that I turned it off. Also why all of the sudden is this an issue as I have been running both for years?

more options

you may be seeing it now because you were migrated to a 64bit build of firefox - some external programs hooking into it may need to adapt. newer versions of kaspersky shouldn't be affected by this incompatibility anymore as well...

https://bugzilla.mozilla.org/show_bug.cgi?id=1268470