Closed Bug 1749915 Opened 4 years ago Closed 4 years ago

Firefox (GeckoMain) using 100% CPU, unable to request pages, on Ubuntu 18

Categories

(Core :: Networking, defect)

Firefox 96
x86_64
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 1749910

People

(Reporter: risnes, Unassigned)

Details

Steps to reproduce:

Start firefox

Actual results:

According to top, a process called GeckoMain consumes ~100% CPU even if the browser is idle (in safe mode, with no web pages open except the local browser start page). Closing the browser does not kill this process.

Expected results:

GeckoMain should consume little CPU when the browser is idle.

strace indicates the process is stuck in a poll loop:

recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)
recvmsg(4, {msg_namelen=0}, 0)          = -1 EAGAIN (Resource temporarily unavailable)```

Also, the browser is unable to request pages. All requests have status Blocked with NS_BINDING_ABORTED in the Transferred-column in the network tab of the dev tools.

I have the same problem on Debian 10. I just updated to Firefox 96 and the browser became unusable.

Component: Untriaged → General
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Summary: Firefox (GeckoMain) using 100% CPU on Ubuntu 18 → Firefox (GeckoMain) using 100% CPU, unable to request pages, on Ubuntu 18
Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.