Bug 63410

Summary:	[Gtk] Webkit not closing sockets resulting in CLOSE_WAIT
Product:	WebKit	Reporter:	David <david>
Component:	New Bugs	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED CONFIGURATION CHANGED
Severity:	Major	CC:	aperez, bugs-noreply, marco
Priority:	P2
Version:	528+ (Nightly build)
Hardware:	PC
OS:	Other

Description David 2011-06-26 14:22:08 PDT

Using a web browser (xxxterm) with WebKitGTK 1.4.1, nearly all connections result in CLOSE_WAIT eating up all available file descriptors.  It seems the server does a close(), but WebKit fails to close() the socket.

I have also tried compiling webkitgtk with --enable-web-sockets=no, but that provided no change.

Comment 1 David 2011-06-27 06:55:22 PDT

I also tested webkit 1.4.1 with midori.  The same issue exists;  lots of CLOSE_WAITs.

Comment 2 Marco Peereboom 2011-07-11 11:49:13 PDT

I tried this with 1.4.2 and see the same results.  Disabling web sockets does seem to remove the CLOSE_WAITs and seems to recycle file descriptors quicker.  Anyone looking at this?

Comment 3 Adrian Perez 2022-04-08 00:19:33 PDT

This bug is for a very old WebKitGTK, from the WebKit1 days. We are
using WebKit2 and the libsoup minimum version required now is much
newer -- I expect this is no longer an issue, but feel free to reopen
if needed.

=]