Hi Cyril, On Sun, Jan 10, 2010 at 12:30:14AM +0100, Cyril Bonté wrote: > Hi Willy, > > Le Samedi 9 Janvier 2010 14:01:36, Willy Tarreau a écrit : > > (...) > > > One thing I suspect would be that we simply fail to free lots of > > allocated memory and that the last pool_alloc() returns NULL due > > to lack of memory, hence the segfault. But I also suspect that we > > *may* end up corrupting some lists or pools if we reuse some data > > across two consecutive requests. Anyway I've committed the fix. > > This doesn't directly concern this issue but I've tried to follow all the > pool_alloc2/pool_free2 calls in the code to track memory leaks. > I've found one which only happens when there's already no more memory when > allocating a new appsession cookie : >
Good catch ! Aleks and I have spent some time in the past to track memory leaks in this area. This is a sensible area because it's one where we're dynamically allocating memory. Obviously those two have escaped us. I'm applying your patch. Thanks! Willy
