חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

Firefox 56 crashes at strtup

  • 3 תגובות
  • 1 has this problem
  • 27 views
  • תגובה אחרונה מאת 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