Where do you read this? In “Network buffers: 52 lowest 52” ? Looks like it’s leaking…
In case you opened an UDP socket, you might loose Network Buffers in case you forget to call FreeRTOS_recv(). This risk can be limited by defining ipconfigUDP_MAX_RX_PACKETS. But of course you must call FreeRTOS_recv()to unload the buffers.
Your logging looks strange because most strings are ended with a linefeed only. In puTTY I normally use the Terminal option: “Implicit CR in every LF”.
I’m using picocom on ubuntu, I will check whether can configure it to work more neat
I’m using an aws_tests project from other platform. so it’s mqtt over secure sockets(tcp). I will go deeper later on. the network descriptor is 60 and I remember well the “lowest 52” is the highest water mark of free available descriptors.
from the log most of the time it’s in idle task(and emac task log showed the network buffer drop quickly), when I stop debug it may enter into network up callback to log the network settings(print ip/gateway etc.).