Re: [lwip-users] TCP causing out of mem pool [RAW]

[address@hidden]

I also double-checked our httpd_raw in contrib, and it does kill a 
TIME_WAIT pcb. However, we might want to get rid of the warning in 
memp_malloc somehow because you aren't the first user confused about 
this message.

Out of interest, do other httpds work now or our httpd in contrib, or do 
all work? The reason I'm asking is I might be needing a POST-enabled (or 
even complete CGI-enabled) httpd some time in the next months and wonder 
if I should extend the one in contrib or take an existing one (if there 
is one that is bug-free an freely available)...

Simon


Chris_S wrote:
> > lwIP goes through all 31 PCBs, but should then recycle them from
> > TIME_WAIT either when the timer expires or it needs one and there aren't
> > any free.
> >     
>
> I get it, yes I think it is working. I get a bunch of msgs about out of mem,
> but TCP keeps working now.
>
> I set GCC for -O0 so I could get a decent call stack,
> and I think I found the source of the flaky behavior.
> It appears was due to a task performance trace I had running.
> Appears not entirely critical section safe yet.
> I just shut that section off for now, and no more crashes so far.
>
> I refreshed a bunch of times with IE and FF, not one miss yet.
> Acts a lot more stable now.  I'll leave it running all day.
>
> Thanks,  Chris.
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>
>