Open Bug 1757888 Opened 3 years ago Updated 3 years ago

firefox does no close TCP connection properly

Categories

(Core :: Networking, defect, P3)

Firefox 97
defect

Tracking

()

UNCONFIRMED

People

(Reporter: riegler.b, Unassigned)

Details

(Whiteboard: [necko-triaged])

Attachments

(3 files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:97.0) Gecko/20100101 Firefox/97.0

Steps to reproduce:

  1. start firefox and do nothing in the application, just let the TCP connections idle
  2. on my GNU/Linux platform Ubuntu 20.04LTS distribution I have a socket monitor shell script
    while true; do netstat -ant |grep '18.66.15.'; echo '--'; sleep 1; done
    just wait for the TCP connection 'passive close', it happens after 170 sec
    the firefox side goes into TCP state 'CLOSE_WAIT'
  3. after about 7 minutes (420 sec) I terminated the firefox application.
  4. the TCP state moves into 'LAST_ACK'

Actual results:

this showcase works always and it is a bug in the firefox Browser.
the TCP connection gets a TCP flag FINish, but does not react on the file EOF
(end_of_file) in UserLand.

Expected results:

the firefox Browser should react on the file EOF (end_of_file) in UserLand
and close() or shutdown() the TCPconnection
by triggering a TCP flag FINish in the opposite direction.
firefox version 97.0 (64-bit)

a wireshark screenshot is appended with the finish of one TCP connection.

The Bugbug bot thinks this bug should belong to the 'Core::Networking' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Networking
Product: Firefox → Core

I added a IPv4 address mapping to wireshark and repeated the test.

  1. start firefox , do nothing and terminate after 5 minutes (300 sec)
    the wireshark started a fresh measurement (timestamps) and immediately after the firefox is started.

  2. "netstat -ant" showes this socket info after firefox termination. (state LAST_ACK)
    Proto Recv-Q Send-Q Local Address Foreign Address State
    tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN
    tcp 1 1 10.0.0.2:53344 18.66.15.49:443 LAST_ACK

  3. filter this TCPconnection in wireshark
    show START_firefox of TCP connection (timestamp 0.855 sec)
    show END_firefox of TCP connection
    the server made the first TCP flag FIN (timestamp 172.026 sec), no reaction from client side. (passive close,TCP state CLOSE_WAIT)
    the firefox process terminated (timestamp 301.191 sec) TCP state LAST_ACK, kernel cleanup

Attached image START_firefox.png
Attached image END_firefox.png
Severity: -- → S4
Priority: -- → P3
Whiteboard: [necko-triaged]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: