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

[Chris Hultqvist]

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

Brendan, I hope we can agree on the following:
A memory leak is 1. Memory allocation that is never freed. 2. It is not done
intentionally (permanent allocation on the heap)
This means that allocations being kept beyond regular use and only returned
after some sort of timeout is not a leak.
Somewhere I read that whenever a new PCB is needed it is allocated permanently
never to be freed and used over and over again. This is not a memory leak
either.
I managed to stress-test my system over a long period of time and remaining
heap space kept decreasing. That is a memory leak. I might be able to make
some more testing this coming fall.
I can  perfectly understand your point wanting to terminate the connection
altogether instantly. Probably you have secondary effects from the presence of
the zombie connection.
I don't know a lot about the TCP protocol (particularly the difference between
FIN and RST), but it seems to me that once you want the connection to
terminate there should be only one single way to do it. What could be gained
by letting the connection hang around for a while?


    _______________________________________________________

Reply to this item at:

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

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

signature.asc
Description: PGP signature