Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox crashes

  • 2 antwoorden
  • 3 hebben dit probleem
  • 2 weergaven
  • Laatste antwoord van harrison.davies

harrison.davies
harrison.davies
more options

Crash ID: bp-4baf1fc9-8748-440f-a098-e78e02160913 Crash ID: bp-4e833778-9b91-4956-9386-df0182160913

Firefox will not start and keeps displaying the crash reporter instead of opening, starting in safe mode doesn't work either. I've tried using version 39.0.3 and version 40.0, I am using these older versions as I write automated test scripts and they do not work on your more recent browser versions. (Something you should also look into)

Any thoughts as to why firefox has just decided to randomly start doing this?

Crash ID: bp-4baf1fc9-8748-440f-a098-e78e02160913 Crash ID: bp-4e833778-9b91-4956-9386-df0182160913 Firefox will not start and keeps displaying the crash reporter instead of opening, starting in safe mode doesn't work either. I've tried using version 39.0.3 and version 40.0, I am using these older versions as I write automated test scripts and they do not work on your more recent browser versions. (Something you should also look into) Any thoughts as to why firefox has just decided to randomly start doing this?

Alle antwoorden (2)

philipp
philipp
  • Moderator
more options

hi harrison.davies, you are likely seeing another instance of bug 1302343. in case you cannot get updated to the current version of firefox, you'll probably have to get in contact with symantec's support to inquire if they can provide a signature update that fixes the crashing issue again or if there is a way to roll back their prior update...

harrison.davies
harrison.davies Vraageigenaar
more options

Will get in touch with my IT dept. to see if they can resolve this symantec issue, thanks