Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Etsi tuesta

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.

Lue lisää

Ketju on arkistoitu. Esitä kysymys, jos tarvitset apua.

Firefox does not connect to any website and crashes on exit

  • 3 vastausta
  • 1 henkilöllä on sama ongelma
  • 13 näyttöä
  • Viimeisin kirjoittaja i-anony

i-anony
i-anony
more options

Firefox 96 cannot connect to any website, even in local network or to send crash reports. One of Firefox processes constantly loads 1 cpu core. On trying to close Firefox, crash happens.

Error persists even in Troubleshooting mode, with new profile and reinstalled Firefox. With older Firefox 88 I don't have this problem.

Environment: Windows 10, Firefox 96.0

Firefox 96 cannot connect to any website, even in local network or to send crash reports. One of Firefox processes constantly loads 1 cpu core. On trying to close Firefox, crash happens. Error persists even in Troubleshooting mode, with new profile and reinstalled Firefox. With older Firefox 88 I don't have this problem. Environment: Windows 10, Firefox 96.0

Valittu ratkaisu

Disabling http3 solved the issue

Lue tämä vastaus kontekstissaan 👍 0

Kaikki vastaukset (3)

Copycat
Copycat
more options

Seem to be working now

Paul
Paul
  • Top 25 Contributor
  • Moderator
more options

Hi

I appreciate that you may have done this already, but please can you restart Firefox which should resolve this issue.

i-anony
i-anony Kysymyksen kysyjä
more options

Valittu ratkaisu

Disabling http3 solved the issue