Sockets not actually closing

GoogleCodeExporter commented 8 years ago

Once I create a new socket, and close it either via the destructor, or via 
the close() function, the object destroyed but the underlying native 
socket is kept open.

This causes the app to hit the "too many open files" limit on Linux, and 
severaly impacts it's operation.

Attached is a repro-case.

I'm checking the amount of used sockets via the:
ls /proc/ID/fd | wc -l - where ID  is the id of the process.

Any idea?

Original issue reported on code.google.com by Stas.Os...@gmail.com on 9 Feb 2010 at 9:57

Merged into: #7

Attachments:

Repro.txt

GoogleCodeExporter commented 8 years ago

One more point - it happens ONLY if there nothing answering on the other side.

If there anything answering, all is fine.

Original comment by Stas.Os...@gmail.com on 9 Feb 2010 at 10:13

GoogleCodeExporter commented 8 years ago

This ticket is actually a duplicate of ticket 7 (which also includes a fix) so 
it
might be deleted.

Original comment by Stas.Os...@gmail.com on 11 Feb 2010 at 6:51

GoogleCodeExporter commented 8 years ago

Original comment by ckkohl79 on 7 Apr 2010 at 9:06

Changed state: Duplicate

dpathakj / junixsocket

Sockets not actually closing #8