Closed
Bug 35997
Opened 25 years ago
Closed 25 years ago
mozilla leaves too many connections in CLOSE_WAIT state
Categories
(Core :: Networking, defect, P3)
Core
Networking
Tracking
()
People
(Reporter: cesarb, Assigned: gagan)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.14 i586; en-US; m15)
BuildID: 2000041505
mozilla does not seem to be closing its local sockets. Leaving connections in
CLOSE_WAIT state is pointless and might be a waste of resources (since it
doesn't seem to timeout, and the only way to make them all get to close is
quitting mozilla)
Reproducible: Always
Steps to Reproduce:
1. Open a xterm window with netstat -tc running
2. Start mozilla and browse some pages
Actual Results: Lots of connections are left open in CLOSE_WAIT state which
doesn't seem to go away.
Expected Results: Closed the local socket so they turn to CLOSE and then go away.
|
||
Comment 2•25 years ago
|
||
This causes mozilla to kill winsock on Win98 after a while. Bug 36660
describes how. I'm going to mark this as affecting all platforms and operating
systems, and bump up the severity.
Bug 36660 says that on Win98, you often end up with lots of ESTABLISHED in
addition to CLOSE_WAIT.
Severity: minor → major
OS: Linux → All
Hardware: PC → All
|
||
Comment 4•25 years ago
|
||
i'm marking this as a dup of 35150 per dark@dnmi.no
if this shows up again, i suppose we'll reopen it.
*** This bug has been marked as a duplicate of 35150 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•