[EXT_EP-9343] SlNetSock_close() leaks memory if underlying interface's close() fails - Software Issue Report (SIR)

XML

Word

Printable

Product:
Network Services
Internal ID:
NS-249
Found In Release:
NS_2_60_00
Fix In Release:
NS_2_70_00
Release Notes:

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