Uploaded image for project: 'LWIP based TCP/IP'
  1. LWIP based TCP/IP
  2. PSLWIP-483

UDP socket resource not freed after close

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: V5.0.2.0, V5.1.0.0, V5.2.0.0, V5.3.0.0
    • Fix Version/s: V5.1.0.14, V5.2.0.8, V5.3.0.1, V5.3.1.0
    • Labels:
      None
    • Account:
      SPC TCP_IP (SPCTCPIP)

      Description

      If the application creates a UDP socket using lwIP Posix api function "lwip_socket()" or lwIP low level api "udp_new()" the socket resource (pcb) is allocated from a resource pool. However, when the application closes such a socket, the socket resource is not released to the pool causing a resource leak.

      It is expected that the socket resource is released back to the resource pool.

      The problem does not affect UDP Sockets allocated with Hilscher specific API  "LwIP_Socket_Alloc()", "LwIP_Socket_Socket()" and the Socket API exposed via DPM mailbox to  applications.

        Attachments

          Issue Links

            Expenses

              Activity

                Status Description

                  People

                  • Reporter:
                    MSchulz Matthias Schulz
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: