Re: [lwip-users] memory leak ?

[Noam weissman]

Hi,

I have checked my code and I made some changes to it. I am sure that I
am freeing 
all the buffers I am getting in recv but still I am getting the folloing
message:

tcp_receive: valid queue length
tcp_write: pbufs on queue => at least one queue non-empty

Also I am getting into an endless loop in tcp_out.c on line 937
    for (; useg->next != NULL; useg = useg->next);

useg->next  = useg ???

------------------------------------------------------------------------
---- 

When I start getting the error message and close the client connection,
wait for a few seconds and
start again it take some time until I get the above messages again.

This indicates that the TCP stack has freed some buffers in the
meantime.
I am not sending or receiving lots of data so this is very strange.

Any ideas ?

Thanks,
Noam.

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Sergio R. Caprile
Sent: Thursday, June 04, 2015 12:02 AM
To: address@hidden
Subject: Re: [lwip-users] memory leak ?

Tx: yes
Rx: if you free them properly then they shouldn't be scarce. Have you
tested this ?

I'm not familiar with lwIP under RTOS except that you must adhere to the
general rule of not calling the stack from different threads.
You should check your port with a known good application first. Try
echo, for example, or netio; both are available in the contrib tree (and
there is nice patch for netio sent by youknowho)


_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

 
 
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************






************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************