[lwip-devel] [bug #49392] TCP leaks memory when LWIP_TCPIP_CORE_LOCKING_INPUT disabled.

[Simon Goldschmidt]

Update of bug #49392 (project lwip):

                Category:                     TCP => Platform ports         
                Severity:              3 - Normal => 2 - Minor              
                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

The only real difference between the LWIP_TCPIP_CORE_LOCKING_INPUT settings is
that when it is 0, you pass input messages via a message queue. So I could
imagine you lose messages that don't fit into your queue. However, both this
and the freeing of RX pbufs that don't get accepted are in the responsibility
of your port or netif driver, so I don't think there's much chance in fixing
this in our lwIP code...

You'll have to come up with more details: try to find out what's in the leaked
memory (RX pbufs or what else)? Also, check what your driver does when
'netif->input()' returns != ERR_OK.

And ensure your port's 'sys_mbox_trypost()' returns != ERR_OK when the mbox is
full. Then, there could still be a bug in your port's implementation of that
function in that you think entries are written but they aren't.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49392>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/