Closed
Bug 1492781
Opened 6 years ago
Closed 2 years ago
Slow browser connections seem to end up in spin loops
Categories
(Core :: Graphics: WebRender, defect, P4)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: djc, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: nightly-community)
Whenever I'm on a very slow or unresponsive web site, Firefox (recent Nightly on macOS) spins up the CPU hard, causing my laptop's fan to blow and the battery to empty relatively quickly.
Reporter | ||
Updated•6 years ago
|
Keywords: nightly-community
Updated•6 years ago
|
Component: General → Networking
Product: Firefox → Core
Reporter | ||
Comment 1•6 years ago
|
||
I do have WebRender enabled, so I was thinking it might even be due to WebRender being inefficient about animating the throbber.
Updated•6 years ago
|
Component: Networking → Graphics: WebRender
Updated•6 years ago
|
Priority: -- → P4
Comment 2•6 years ago
|
||
Bug 1461239 fix might make cpu usage more efficient than before.
Comment 3•6 years ago
|
||
How much worse is the problem with webrender on vs off?
Flags: needinfo?(dirkjan)
Comment 4•6 years ago
|
||
a URL that simulates "slow connections" is https://jwatt.org/tmp/load-never-finishes.php
Comment 5•6 years ago
|
||
WR: https://perfht.ml/2ytk7hm
non-WR: https://perfht.ml/2yw9x9o
These profiles are after the CPU use has settled down
observation: With WR, CPU goes to 100%, then comes down and settles in 10 seconds or so. Spikes a bit during this times
Non-WR: settles down almost immediately
Reporter | ||
Comment 6•6 years ago
|
||
Actually, it looks like there's not a big difference for me in terms of WebRender vs non-WebRender. Both end up spinning the CPU hard for me.
Flags: needinfo?(dirkjan)
Updated•6 years ago
|
Blocks: stage-wr-backlog
Reporter | ||
Comment 8•2 years ago
|
||
I'm using release now, but I cannot reproduce this.
Flags: needinfo?(dirkjan)
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
OS: Unspecified → macOS
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•