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

[Chris_S]

> By "dies", you mean it crashes, or just stops responding to new
> connections?

Well by die I mean TCP no longer responding.  TCP is dead.
ICMP still works.

But now with FireFox, it crashes hard => Dabort.
I get a number of behaviors.  Flaky.

I put the wireshark list in the other post.

Chris.



 
> > I tried changing TCP_MSL from 60000 to 6000,
> > and it sure had an effect.  I saw some TCB blocks being reallocated,
> > but again after more refreshes it finally crashed the CPU and went to
> > restart.
> 
> That is bad.  I think we need to investigate this further.
> 
> > I had KEEPALIVE turned ON, and tried it OFF, still the same.
> > 
> > I noticed an old bug 24830 that seems like the same thing.
> > Not fixed yet, says v1.4
> 
> Doesn't sounds like the same thing to me: that wouldn't cause a crash.
> Should be simple to test though, either with a packet capture, or by
> looking at the state of the PCBs in the tcp_active_pcbs list with a
> debugger
> 
> Kieran
> 
>