Hi László, On Fri, Sep 05, 2014 at 10:08:23AM +0200, Sárközi, László wrote: > Dear haproxy list, > > While running haproxy master with valgrind and sending a SIGTERM to > terminate the proxy, valgrind found a memory leak -- the config file name > was not freed properly in the deinit() function.
In general we try to be very careful when adding extra free() to deinit(), because we already caused regressions in the past when trying to please valgrind. The usual thing is a double-free causing an abort() and the process to dump a core upon exit. That remains unnoticed until an admin or a script brings that core back for analysis, and everyone wastes time. Here however, your fix seems valid, so I'm applying it. Thanks! Willy
