Hi Cyril,

On Sat, Jan 09, 2010 at 01:47:33PM +0100, Cyril Bonté wrote:
> Maybe this sessid should be stored in "struct http_txn" instead of "struct 
> session" (for readability).

Good idea. I'll see if I can find some time to do this.

> > I tried to reproduce the issue but failed to do so, reason why I'm
> > asking for a test.
> 
> Same here, I can't reproduce it.
> Bart, is it quickly reproducible or does it happen after a lot of traffic ? 
> How much memory does haproxy use when it segfaults (I find the appsession 
> timeout quite big) ?

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.

Regards,
Willy


Reply via email to