[reSIProcate] resiprocate stack memeory leak?????

[FrankYuan]

Hi All,

I used svn to get the latest resip stack on Aug. 4, 2006 and build a 
simple applications.
If the call rate is  20 per second, there is no memory leak (the memory 
status stable) and stay about 200 mega bytes.
If the calls rate is 100 to 200 per second, the memory usage increases 
dramatically from 200 megabytes to about 400 megabytes for 2 hour durations.
The memory usage will not go down even after the call generator stopped  
for more than 4 hours.

So valgrind is used to monitor the memory leak, and it did not show any.

 resiprocate stack must hold the memory.

I try to use the size of mStateMachineFifo to control the number of  
incoming sip  request msg if the size exceeds certain limit, but the 
size may get wrong size of NoSize defined by AbstractFifo.hxx when clear 
func is called.

My question about  rutil/AbstractFifo.hxx:
     since std::deque mFifo is defined, there is no need to define mSize 
since the size of msg can get from mFifo.size().
     Why mSize is assigned NoSize which is 0U-1 when func clear is 
called.  mSize should be 0 fro this case.
     So mStateMachineFifo.size cannot be trusted since it can be 0U-1 
even if the mFifo is empty after clear() is called.

-- 
Thanks

Frank Yuan