On Sat, Jul 04, 2020 at 10:17:50AM +0200, William Dauchy wrote: > Hello Willy, > > On Sat, Jul 4, 2020 at 8:11 AM Willy Tarreau <w...@1wt.eu> wrote: > > HAProxy 2.2-dev12 was released on 2020/07/04. It added 72 new commits > > after version 2.2-dev11. > > maybe the package is being uploaded but I can't find it on > http://www.haproxy.org/download/2.2/src/devel/
Ah this is because I'm stupid :-) On haproxy.org we run with *all* debugging and strict options available (including the expensive DEBUG_UAF), that's how I detected the issue when building with DEBUG_LOCK. And working on fixing this while I was typing the announce message, I simply forgot to type "publish-and-update" :-) It's fixed now. > > > - for developers, building with DEBUG_MEM_STATS provides a new expert > > command "debug dev memstats" which shows the total counts (calls and > > sizes) of memory allocations per line of code. This is very cheap and > > can be enabled on production servers if suspecting a memory leak > > somewhere (and it served to spot a regression in a recent fix). > > without forgetting the useful reset argument, "debug dev memstats > reset" which then allows you to see the allocation starting from a > specific moment. Yes, I thought it was really needed. Also please note that this doesn't count the free() calls as it uses #define and a few variables are called "free", so there's no difference and one has to use it as an aid and nothing else. But when you see 3 GB missing from your memory and you spot a line which totalled 3 GB since last reset, it definitely encourages to go into that direction first ;-) Cheers, Willy
