[EXT_EP-9343] SlNetSock_close() leaks memory if underlying interface's close() fails Created: 02/May/19 Updated: 19/Feb/20 Resolved: 02/May/19 |
|
| Status: | Fixed |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | Network Services |
| Internal ID: | NS-249 |
| Found In Release: | NS_2_60_00 |
| Fix In Release: | NS_2_70_00 |
| Release Notes: | 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. |
| Description |
|
SlNetSock_close() leaks memory if underlying interface's close() fails |