be65de0d09
In "connect" all networks are removed and new network is always added, but in disconnect the network isn't deleted, so, the memory is unnecessarily held till next connect. This is not exactly a leak, but if someone profiles using "kernel heap" then this can be construed as a leak. Fix this by removing network during the disconnection (for now "all") so that the memory can be used by someone else. Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| acpica | ||
| canopennode | ||
| cmsis | ||
| cmsis-dsp | ||
| cmsis-nn | ||
| fatfs | ||
| hal_ambiq | ||
| hal_ethos_u | ||
| hal_gigadevice | ||
| hal_infineon | ||
| hal_nordic | ||
| hal_nxp | ||
| hal_rpi_pico | ||
| hal_st | ||
| hostap | ||
| liblc3 | ||
| littlefs | ||
| loramac-node | ||
| lvgl | ||
| lz4 | ||
| mbedtls | ||
| nanopb | ||
| openthread | ||
| percepio | ||
| segger | ||
| tflite-micro | ||
| thrift | ||
| trusted-firmware-a | ||
| trusted-firmware-m | ||
| uoscore-uedhoc | ||
| zcbor | ||
| Kconfig | ||
| Kconfig.altera | ||
| Kconfig.atmel | ||
| Kconfig.chre | ||
| Kconfig.cypress | ||
| Kconfig.eos_s3 | ||
| Kconfig.esp32 | ||
| Kconfig.imx | ||
| Kconfig.infineon | ||
| Kconfig.intel | ||
| Kconfig.libmetal | ||
| Kconfig.mcuboot | ||
| Kconfig.mcux | ||
| Kconfig.microchip | ||
| Kconfig.nuvoton | ||
| Kconfig.nxp_s32 | ||
| Kconfig.open-amp | ||
| Kconfig.picolibc | ||
| Kconfig.renesas_fsp | ||
| Kconfig.rust | ||
| Kconfig.silabs | ||
| Kconfig.simplelink | ||
| Kconfig.sof | ||
| Kconfig.stm32 | ||
| Kconfig.sysbuild | ||
| Kconfig.syst | ||
| Kconfig.telink | ||
| Kconfig.tinycrypt | ||
| Kconfig.vega | ||
| Kconfig.wurthelektronik | ||
| Kconfig.xtensa | ||
| modules.cmake | ||