[lwip-devel] [bug #62231] LwIP tcp socket stalls when "plug pulled", creates leak when closed

[Chris Hultqvist]

Follow-up Comment #2, bug #62231 (group lwip):

Hi Brendan and thanks for the input

Interesting. It has been a while and I have since migrated the server side to
an Raspberry Pi for various reasons.

My memory has faded slightly but I remember that closing the socket actually
worked because the number of allowed connections is very limited in the ESP
IDF framework and rapidly saturated when client modules were abruptly reset
and started up again as a new connection. When the old ones were identified
and killed, the only remains were small chunks of memory on the heap that
didn't go away after the TCP time-out.

It does seem probable that this memory corresponds to pending socket transfer
data, but it should in my view be freed in the "lwip_close(socket)" call.

I would really like to test your approach to see if that stops the module from
leaking memory, but currently I have no setup that enables me to do so.

My conclusion is that our cases differ in that I managed to close the
identified stalled socket while you didn't. The suggested lingering option may
have resolved the leak.


    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?62231>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/

signature.asc
Description: PGP signature