Closed Bug 1651541 Opened 5 years ago Closed 5 years ago

MainThread uses 100% of 1 CPU thread when http3 is enabled

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Version:
79 Branch
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1648553

People

(Reporter: abdilra7eem, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

  1. Set network.http.http3.enable to 'true' on FireFox Developer Edition 79.0b5 (64-bit) on Fedora Linux x86_64 (I haven't tested with other versions/systems).
  2. close and re-open it.

Actual results:

The MainThread process uses 100% of 1 CPU core.
When closing FireFox, the MainThread stays as is until I kill it.
This behaviour repeats every time (Even with all extensions and plug-ins disabled).

Component: Untriaged → Networking
Product: Firefox → Core

Happens to me too on macOS on the same Firefox version. But it only happens after I visit a website supporting QUIC. Firefox is then unresponsive even if I close that tab. Command + Q doesn't work and I need to force quit it.

mozreg found this range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9b981fcfb6ac3119837605e3189c5832446c77ab&tochange=0a4b3f99d2d1b0a6aa73754e38da82a3b58f5635

This was fixed in bug 1648553.

May I double check which version of Firefox are you running?

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Flags: needinfo?(mcccs)
Flags: needinfo?(abdilra7eem)
Resolution: --- → DUPLICATE

79.0b5 developer edition

Flags: needinfo?(mcccs)

I updated to Beta 6, and the problem seems to have disappeared (even with addons and plugins enabled).
I also ran the tests against https://quic.nginx.org/quic.html , and it seems to work quite well (over 2950 requests are served using quic, and less that 50 failed). No serious performance problems in the browser.

Flags: needinfo?(abdilra7eem)

(In reply to A. Fakhouri from comment #4)

I updated to Beta 6, and the problem seems to have disappeared (even with addons and plugins enabled).
I also ran the tests against https://quic.nginx.org/quic.html , and it seems to work quite well (over 2950 requests are served using quic, and less that 50 failed). No serious performance problems in the browser.

bug 1648553 has been uplifted and it is in beta 6.

thank you for reporting the issue!

You need to log in before you can comment on or make changes to this bug.