SlNetSock_close() leaks memory if underlying interface's close() fails

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Medium
    • Network Services
    • NS-249
    • NS_2_60_00
    • NS_2_70_00
    • Hide
      SlNetSock_close() does not free virtual socket resources if the underlying interface's sockClose() call fails.

      An example of when this might happen is in the case that a sync loss occurs between a host MCU and a CC3120, which can result in SL_API_ABORTED being returned to the application and the CC3120 host driver setting the SL_RESTART_REQUIRED bit in the status variable.

      SlNetSock_close() will have a new policy to always "free as much as possible". It will still return failure if the underlying interface close fails, but all SlNetSock-related resources will be freed.
      Show
      SlNetSock_close() does not free virtual socket resources if the underlying interface's sockClose() call fails. An example of when this might happen is in the case that a sync loss occurs between a host MCU and a CC3120, which can result in SL_API_ABORTED being returned to the application and the CC3120 host driver setting the SL_RESTART_REQUIRED bit in the status variable. SlNetSock_close() will have a new policy to always "free as much as possible". It will still return failure if the underlying interface close fails, but all SlNetSock-related resources will be freed.

      SlNetSock_close() leaks memory if underlying interface's close() fails

            Assignee:
            TI User
            Reporter:
            TI User
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:

                Connection: Intermediate to External PROD System
                EXTSYNC-1846 - SlNetSock_close() leaks memory if u...
                SYNCHRONIZED
                • Last Sync Date: