1889621 - A repeating 1h "nsHttpConnectionMgr" timer fires while GeckoView example is completely idle

Status: NEW

(Core :: Networking: HTTP, defect, P2)

Description

[Florian Quèze [:florian]]

I captured a long (2+hours) power profile of gecko view example being idle: https://share.firefox.dev/43IpfMS

During that time I had only 2 wake-ups caused by timers. Apparently nsHttpConnectionMgr has a 1h repeating timer.

Discussion on matrix:

acreskey:

That looks like this one:
https://searchfox.org/mozilla-central/rev/d7c5387a43bda5163afcb9e65e17c476c6ecf625/netwerk/protocol/http/nsHttpConnectionMgr.cpp#3406-3425
Used to search of half-open connections (also used for h2)
https://searchfox.org/mozilla-central/rev/d7c5387a43bda5163afcb9e65e17c476c6ecf625/netwerk/protocol/http/nsHttpConnectionMgr.h#371-375
Apparently if there are no connections, the timer should be disabled.

florian:

the markers in the socket thread say "SocketTransportService::Poll - Poll count: 3, Poll timeout: NO_TIMEOUT", so it seems we have 3 sockets, whatever they are

Comment 1

[Valentin Gosu [:valentin] (he/him) {{ FYI: OOO 14 June - 4 August }}]

I think the consensus here was that we'd try to avoid setting the timer to 1 hour.
We probably did this to avoid cancelling the timer instead - but cancelling seems like the correct call when the timeout is set to max - 1hr.