RaceCacheWithNetwork is racing on 5G cellular networks
Categories
(Core :: Networking: Cache, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox87 | --- | fixed |
People
(Reporter: acreskey, Assigned: valentin)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files)
There is logic in place so that we don't RaceCacheWithNetwork when the user is on a cellular network (to avoid excess data usage).
See Bug 1377570.
However on 5G cellular networks, the network type is not being correctly identified, and is reported as nsINetworkLinkService::LINK_TYPE_UNKNOWN
.
I can see this in logs via an instrumented build that I made:
nsHttpChannel::MaybeRaceCacheWithNetwork: netLinkType 0
See the link type enumeration here.
Further logs have shown that we are in fact racing cache with network when on 5G cellular.
Assignee | ||
Comment 1•5 years ago
|
||
Thanks for the report. This is a good point.
I think we should:
- Make geckoview code report a 5G network when necessary
- Not race for UNKNOWN network types on Android (doesn't seem like a huge loss)
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Depends on D103305
Reporter | ||
Comment 4•5 years ago
|
||
(In reply to Valentin Gosu [:valentin] (he/him) from comment #1)
Thanks for the report. This is a good point.
I think we should:
- Make geckoview code report a 5G network when necessary
- Not race for UNKNOWN network types on Android (doesn't seem like a huge loss)
I think not racing for UNKNOWN on Android is a great future-proof solution.
(And of course Android devices don't have slow platter drives, so in the unlikely event of a wifi or wired connection being identified as UNKNOWN, the loss is small).
And great to see a same day patch.
Comment 6•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/edeb8bba12e8
https://hg.mozilla.org/mozilla-central/rev/924b2e399c4b
Description
•