FF takes long time to start when system sets public DNS
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: sky96111, Unassigned)
Details
Attachments
(1 file)
|
3.73 MB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.5060.134 Safari/537.36
Steps to reproduce:
- Link to a network which provides public DNS in DHCP (in my case is Ali DNS: 223.5.5.5, 223.6.6.6)
- Launch FireFox 102
Actual results:
It takes about 1 min to start into the first page
Expected results:
It should start within seconds.
But if the network provides local DNS resolver(e.g. OpenWrt DNSMASQ provide 192.168.1.1 or mobile hotspot), FF starts properly.
In "strace firefox" found FF stucks in several timeout like:
connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.62.73")}, 16) = 0
poll([{fd=15, events=POLLOUT}], 1, 0) = 1 ([{fd=15, revents=POLLOUT}])
sendto(15, "\5d\1\0\0\1\0\0\0\0\0\0\vSurfaceSUSE\4DHCP\0\0\1"..., 34, MSG_NOSIGNAL, NULL, 0) = 34
poll([{fd=15, events=POLLIN}], 1, 5000) = 0 (Timeout)
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 16
setsockopt(16, SOL_IP, IP_RECVERR, [1], 4) = 0
connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("223.5.5.5")}, 16) = 0
poll([{fd=16, events=POLLOUT}], 1, 0) = 1 ([{fd=16, revents=POLLOUT}])
sendto(16, "\5d\1\0\0\1\0\0\0\0\0\0\vSurfaceSUSE\4DHCP\0\0\1"..., 34, MSG_NOSIGNAL, NULL, 0) = 34
poll([{fd=16, events=POLLIN}], 1, 3000) = 0 (Timeout)
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 17
setsockopt(17, SOL_IP, IP_RECVERR, [1], 4) = 0
connect(17, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("223.6.6.6")}, 16) = 0
poll([{fd=17, events=POLLOUT}], 1, 0) = 1 ([{fd=17, revents=POLLOUT}])
sendto(17, "\5d\1\0\0\1\0\0\0\0\0\0\vSurfaceSUSE\4DHCP\0\0\1"..., 34, MSG_NOSIGNAL, NULL, 0) = 34
poll([{fd=17, events=POLLIN}], 1, 6000) = 0 (Timeout)
poll([{fd=15, events=POLLOUT}], 1, 0) = 1 ([{fd=15, revents=POLLOUT}])
Comment 1•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
(In reply to Kershaw Chang [:kershaw] from comment #2)
Could you try to capture a http log?
Thanks.
Sorry, the problem disappeared after one night. I will close it
Description
•