9 ms·

What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in t

What worked for me was disabling HTTP3 support with the 'network.http.http3.enabled' key in about:config and then restarting Firefox. Seems like it's stuck in the 'SocketThread', repeatedly doing this: 2022-01-13 08:20:53.075936 UTC - [Parent 4106991: Socket Thread]: V/nsHttp Http3Stream::OnReadSegment count=333 state=4 [this=7f6e295623a0]

madzi 5y ago
If only we had transporter tech, I would send you a keg.
Ennea 5y ago
I can confirm that disabling HTTP3 support helps. Thank you for the workaround.
hpjules 5y ago
This worked for me as well. Thanks!
starwatch 5y ago
I had to force quit and restart, but that seemed to do the trick for me too. Thank you!
- smcl 5y ago
  I had something similar - changed the setting, closed firefox, opened it again and was presented with the message "Another instance of Firefox is already running. Please close other instances of Firefox". There was a firefox.exe process running 12% (on an 8-core machine, so it was pegging one core at 100%) that I had to kill. After that FF worked fine.
killdozer 5y ago
I had to also turn off DoH but this did resolve my issue, wild.
Ataraxic 5y ago
Thank you this indeed works.
Semaphor 5y ago
Hah, you are on HN as well, just linked to your reddit comment :D
Vincenius 5y ago
also fixed it for me - thanks :)
miohtama 5y ago
It worked. Where can I buy you a beer?
revendell_elf 5y ago
shafyy 5y ago
Thanks a lot! Do we need to enable this again later when they fixed it?
rnd0 5y ago
I did this, posted my earlier comment, then re-enabled that to see if I would be able to load pages or not and I was. The other thing I noticed was that previously when I looked in taskmgr (windows 10) there were 4 or 5 firefox processes going on -but when I went to close firefox after setting that to false there were not. I'll close and check again but I'm wondering if simply setting it to false once doesn't allow it to perform some update or something that lets it get back to behaving normally? Like unsticking a log jam? [edit]Forget I said anything. When I restarted and tried to reload HN it hung again. I had to disable network.http.http3.enabled in order come back and edit this comment.
jesperlang 5y ago
Wow thank you! I was bangning my head against the wall, restarting my computer, disabling extensions, etc. This worked like a charm :)
shsbdncudx 5y ago
I will have your babies, and that’s coming from a straight male.
infinita740 5y ago
Thank you very much! Saved me a lot of time.
jacquesm 5y ago
Oh wow, thank you so much for this. I've been trying to troubleshoot this for hours but because my browser didn't work I never thought of checking HN to see if other people had this as well. Another score for automatic updates I guess.
- Semaphor 5y ago
  As others said, this happened to all kinds of versions, not just 96.
  - jacquesm 5y ago
    I was perfectly happy with the one that didn't support this 'feature', and automatic updates are what brought it to my system.
    - zuhsetaqi 5y ago
      Why don’t you just disable automatic updates?
      - jacquesm 5y ago
        Good question. Because for security reasons you want to stay up-to-date on software that connects to various websites. At the same time, from a functionality point of view I wished I'd never have to update anything.
        zuhsetaqi 5y ago
        Yes it has its pros and cons like everything. But as a default for the average user I think auto update should be enabled
        mikro2nd 5y ago
        It's not a question of avoiding updates altogether, but the sad reality that it always seems to choose the most inconvenient and/or expensive time to do it. If they'd just do as Thunderbird does -- notify me that there's an update and ask me what action I'd like to take -- there'd be no problem. As it is, being unable to choose when the update happens is unacceptable. FWIW I've tried every documented setting, "enterprise" policies, etc. to prevent automatic updates in FF, but nothing seems to stick.
c06n 5y ago
Thank you!
apatters 5y ago
You're a godsend, this stupidity wasted an hour of my time, you fixed it. What a trash joke Firefox has become.
birdyrooster 5y ago
Not working for me.
- justemre 5y ago
  Did you restart the browser?
- anhm 5y ago
  closing all browser windows does not work. I had to `pkill firefox` and it works
  - birdyrooster 5y ago
    Yeah I ended up just waiting 5 minutes and it started working again.
oleks 5y ago
Yep, works. However, you need to magically restart the browser. Apperently, it runs some background processes whose names contain neither the character sequence "firefox", nor "mozilla", according to pgrep.
- foxfluff 5y ago
  GeckoMain
- mjochim 5y ago
  pgrep -f and pkill -f probably do the trick.
ilovefood 5y ago
Thank you very much, this fixed it for me as well! :)
Dentrax 5y ago
It worked, thanks! How can we check the Firefox's logs?
deleted 5y ago
[deleted]
MaurizioPz 5y ago
Many other have already said it, but I want to add my voice too. Thanks!
Raed667 5y ago
This comment should be higher. Thank you.
brabel 5y ago
I only had to do a hard restart (force quit it, as others point out, just closing the window causes FF to hang). After restarting, everything seems to work fine. EDIT: my FF version is 91.5.0esr (64-bit) on MacOS. Many of my colleagues had the same issue today, and they all report that just restarting FF fixes the problem (one restarted the computer itself).
- jacquesm 5y ago
  Give it some time. That's exactly what I did first thing this morning, then it worked again for 20 minutes, then it broke again. And then I couldn't get it to work at all until I saw this message.
mftb 5y ago
Interesting, it first hit me while I was browsing Youtube. I have been noticing aborted/stalled connections specifically on Youtube over the last week or so. I bet you they have http3 going. After upgrading to 96 today was the first time I got all new connections blocked.
- gwd 5y ago
  Yes, I think it first hit me when I was updating gmail. I bet Google enabled something new on their services that Firefox didn't handle properly. (Without knowing any details, it could be that Google is actually doing something non-standards-compliant; but in any case FF should respond gracefully and not hang all connections, even those not going to Google.)
gisho 5y ago
Thanks, this has worked!
folli 5y ago
It seems there's no need anymore, autoupdate fixes the issue since approx 09:25 UTC
- JokerDan 5y ago
  Which Ver number?
skywal_l 5y ago
It's been posted already but putting it here for better visibility: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908
- deleted 5y ago
  [deleted]
- sleepless 5y ago
  Closed as dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1749910 https://bugzilla.mozilla.org/show_bug.cgi?id=1749910 "Firefox has witnessed outages and we are sorry for that. We believe it's fixed and a restart of Firefox should restore normal behaviour. We will provide more information shortly."
fpina 5y ago
Thank you!
delijati 5y ago
I started in in `safe-mode` and assumed it was a addon that did block all traffic. Anyway Thanks

madzi 5y ago

If only we had transporter tech, I would send you a keg.

Ennea 5y ago

I can confirm that disabling HTTP3 support helps. Thank you for the workaround.

hpjules 5y ago

This worked for me as well. Thanks!

starwatch 5y ago

I had to force quit and restart, but that seemed to do the trick for me too. Thank you!

smcl 5y ago
I had something similar - changed the setting, closed firefox, opened it again and was presented with the message "Another instance of Firefox is already running. Please close other instances of Firefox". There was a firefox.exe process running 12% (on an 8-core machine, so it was pegging one core at 100%) that I had to kill. After that FF worked fine.

killdozer 5y ago

I had to also turn off DoH but this did resolve my issue, wild.

Ataraxic 5y ago

Thank you this indeed works.

Semaphor 5y ago

Hah, you are on HN as well, just linked to your reddit comment :D

Vincenius 5y ago

also fixed it for me - thanks :)

miohtama 5y ago

It worked. Where can I buy you a beer?

revendell_elf 5y ago

shafyy 5y ago

Thanks a lot! Do we need to enable this again later when they fixed it?

rnd0 5y ago

I did this, posted my earlier comment, then re-enabled that to see if I would be able to load pages or not and I was. The other thing I noticed was that previously when I looked in taskmgr (windows 10) there were 4 or 5 firefox processes going on -but when I went to close firefox after setting that to false there were not. I'll close and check again but I'm wondering if simply setting it to false once doesn't allow it to perform some update or something that lets it get back to behaving normally? Like unsticking a log jam? [edit]Forget I said anything. When I restarted and tried to reload HN it hung again. I had to disable network.http.http3.enabled in order come back and edit this comment.

jesperlang 5y ago

Wow thank you! I was bangning my head against the wall, restarting my computer, disabling extensions, etc. This worked like a charm :)

shsbdncudx 5y ago

I will have your babies, and that’s coming from a straight male.

infinita740 5y ago

Thank you very much! Saved me a lot of time.

jacquesm 5y ago

Oh wow, thank you so much for this. I've been trying to troubleshoot this for hours but because my browser didn't work I never thought of checking HN to see if other people had this as well. Another score for automatic updates I guess.

Semaphor 5y ago
As others said, this happened to all kinds of versions, not just 96.
- jacquesm 5y ago
  I was perfectly happy with the one that didn't support this 'feature', and automatic updates are what brought it to my system.
  - zuhsetaqi 5y ago
    Why don’t you just disable automatic updates?
    - jacquesm 5y ago
      Good question. Because for security reasons you want to stay up-to-date on software that connects to various websites. At the same time, from a functionality point of view I wished I'd never have to update anything.
      - zuhsetaqi 5y ago
        Yes it has its pros and cons like everything. But as a default for the average user I think auto update should be enabled
      - mikro2nd 5y ago
        It's not a question of avoiding updates altogether, but the sad reality that it always seems to choose the most inconvenient and/or expensive time to do it. If they'd just do as Thunderbird does -- notify me that there's an update and ask me what action I'd like to take -- there'd be no problem. As it is, being unable to choose when the update happens is unacceptable. FWIW I've tried every documented setting, "enterprise" policies, etc. to prevent automatic updates in FF, but nothing seems to stick.

c06n 5y ago

Thank you!

apatters 5y ago

You're a godsend, this stupidity wasted an hour of my time, you fixed it. What a trash joke Firefox has become.

birdyrooster 5y ago

Not working for me.

justemre 5y ago
Did you restart the browser?
anhm 5y ago
closing all browser windows does not work. I had to `pkill firefox` and it works
- birdyrooster 5y ago
  Yeah I ended up just waiting 5 minutes and it started working again.

oleks 5y ago

Yep, works. However, you need to magically restart the browser. Apperently, it runs some background processes whose names contain neither the character sequence "firefox", nor "mozilla", according to pgrep.

foxfluff 5y ago
GeckoMain
mjochim 5y ago
pgrep -f and pkill -f probably do the trick.

ilovefood 5y ago

Thank you very much, this fixed it for me as well! :)

Dentrax 5y ago

It worked, thanks! How can we check the Firefox's logs?

deleted 5y ago

[deleted]

MaurizioPz 5y ago

Many other have already said it, but I want to add my voice too. Thanks!

Raed667 5y ago

This comment should be higher. Thank you.

brabel 5y ago

I only had to do a hard restart (force quit it, as others point out, just closing the window causes FF to hang). After restarting, everything seems to work fine. EDIT: my FF version is 91.5.0esr (64-bit) on MacOS. Many of my colleagues had the same issue today, and they all report that just restarting FF fixes the problem (one restarted the computer itself).

jacquesm 5y ago
Give it some time. That's exactly what I did first thing this morning, then it worked again for 20 minutes, then it broke again. And then I couldn't get it to work at all until I saw this message.

mftb 5y ago

Interesting, it first hit me while I was browsing Youtube. I have been noticing aborted/stalled connections specifically on Youtube over the last week or so. I bet you they have http3 going. After upgrading to 96 today was the first time I got all new connections blocked.

gwd 5y ago
Yes, I think it first hit me when I was updating gmail. I bet Google enabled something new on their services that Firefox didn't handle properly. (Without knowing any details, it could be that Google is actually doing something non-standards-compliant; but in any case FF should respond gracefully and not hang all connections, even those not going to Google.)

gisho 5y ago

Thanks, this has worked!

folli 5y ago

It seems there's no need anymore, autoupdate fixes the issue since approx 09:25 UTC

JokerDan 5y ago
Which Ver number?

skywal_l 5y ago

It's been posted already but putting it here for better visibility: https://bugzilla.mozilla.org/show_bug.cgi?id=1749908 https://bugzilla.mozilla.org/show_bug.cgi?id=1749908

deleted 5y ago
[deleted]
sleepless 5y ago
Closed as dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=1749910 https://bugzilla.mozilla.org/show_bug.cgi?id=1749910 "Firefox has witnessed outages and we are sorry for that. We believe it's fixed and a restart of Firefox should restore normal behaviour. We will provide more information shortly."

fpina 5y ago

Thank you!

delijati 5y ago

I started in in `safe-mode` and assumed it was a addon that did block all traffic. Anyway Thanks