Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Avatar for Username

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Wątek został zarchiwizowany. Jeśli potrzebujesz pomocy, zadaj nowe pytanie.

Firefox crashes

  • 3 odpowiedzi
  • 5 osób ma ten problem
  • 6 wyświetleń
  • Ostatnia odpowiedź od philipp

Ebes
Ebes
more options

Hello

Newest Report: Crash ID: bp-d3cf64ba-ace8-44d5-b747-470ed2170130

First Report: Crash ID: bp-5cd84492-aa2f-47b9-afdf-678b22170130

This morning I started my computer and was able to use Firefox just fine. When I closed the browser, I got the "Please wait while Firefox finishes updating" message. I let it do its thing and when I went back into Firefox, it would go to the homepage (normal Firefox one) and then after a few seconds would crash and give me the crash reporter. At one point it asked me to Refresh Firefox and it put the old files on my desktop which I moved to a different desktop folder.

I tried multiple times and eventually uninstalled and reinstalled Firefox. This did not help. At this point Firefox wouldn't even open and automatically gives me a crash reporter. I then restarted my computer and got the same response of an automatic crash reporter.

I tried uninstalling and reinstalling again and that didn't work.

I then tried troubleshooting by making a new profile and deleting the old profile, but keeping the files, but that didn't change anything.

I also tried opening Firefox in Safe Mode, but that didn't work either. I get a Crash Reporter after I click Firefox and before the browser even appears.

Hello Newest Report: Crash ID: bp-d3cf64ba-ace8-44d5-b747-470ed2170130 First Report: Crash ID: bp-5cd84492-aa2f-47b9-afdf-678b22170130 This morning I started my computer and was able to use Firefox just fine. When I closed the browser, I got the "Please wait while Firefox finishes updating" message. I let it do its thing and when I went back into Firefox, it would go to the homepage (normal Firefox one) and then after a few seconds would crash and give me the crash reporter. At one point it asked me to Refresh Firefox and it put the old files on my desktop which I moved to a different desktop folder. I tried multiple times and eventually uninstalled and reinstalled Firefox. This did not help. At this point Firefox wouldn't even open and automatically gives me a crash reporter. I then restarted my computer and got the same response of an automatic crash reporter. I tried uninstalling and reinstalling again and that didn't work. I then tried troubleshooting by making a new profile and deleting the old profile, but keeping the files, but that didn't change anything. I also tried opening Firefox in Safe Mode, but that didn't work either. I get a Crash Reporter after I click Firefox and before the browser even appears.

Wszystkie odpowiedzi (3)

Scribe
Scribe
more options

Hi, this seems to be caused by Websense/Forcepoint software, so if you have it on your system or within your organization, perhaps you could if possible, try updating or disabling it. Also see Old versions of Websense cause startup crashes in Firefox.

If your question is resolved by this or another answer, please take a minute to let us know. Thank you!

Ebes
Ebes Zadający pytanie
more options

I don't think my organization uses Websense or Forcepoint and it worked fine this morning when I started Firefox. It wasn't until after I closed Firefox and then reopened it later (without a computer restart or company software push) that the issue happened.

philipp
philipp
  • Moderator
more options

hello, your crash reports show that this is unfortunately caused by forcepoint/websense endpoint security software that is running on your system, so Scribe's advice applies! please get in contact with your it department about this issue and refer them to the mentioned support article...