Re: [lwip-users] Receive path stuck due to pbuf_alloc returning NULL

[Sebastian Gonzalez]

Hi,

I am still having problems, but it's true that it takes more time for the
system to stop receiving under the same stress tests.
I made a little test that includes a semaphore that is set everytime a pbuf
is allocated and is released every time the packet is processed, but with no
positive results. Wether not every pbuf is freed in the TCP/IP thread after
being processed, or there is a memory leak as Ivan sugested.
Is there any way to release all the memory? I don't mind having to close my
application sockets if the system is restored and I can reopen them.

Thanks.

Sebestian.



--
View this message in context: 
http://lwip.100.n7.nabble.com/Receive-path-stuck-due-to-pbuf-alloc-returning-NULL-tp21461p21482.html
Sent from the lwip-users mailing list archive at Nabble.com.