Re: [BUG] memory leak with treads and stick-table/peers

Hi, no more leak after "BUG/MINOR: memory: Set objects size for pools in the per-thread cache" ++ Manu > Le 5 juin 2019 à 16:13, Emmanuel Hocdet a écrit : > > >> Le 5 juin 2019 à 16:07, Emmanuel Hocdet > > a écrit : >> >> Hi Frederic >> >>> Le 5 juin 2019 à 15:44,

Re: [BUG] memory leak with treads and stick-table/peers

> Le 5 juin 2019 à 16:07, Emmanuel Hocdet a écrit : > > Hi Frederic > >> Le 5 juin 2019 à 15:44, Frederic Lecaille > > a écrit : >> >> On 6/5/19 3:06 PM, Emmanuel Hocdet wrote: >>> Hi, >> >> Hi Emmanuel, >> >>> After switched to haproxy 1.9 with threads

Re: [BUG] memory leak with treads and stick-table/peers

Hi Frederic > Le 5 juin 2019 à 15:44, Frederic Lecaille a écrit : > > On 6/5/19 3:06 PM, Emmanuel Hocdet wrote: >> Hi, > > Hi Emmanuel, > >> After switched to haproxy 1.9 with threads activated, i noticed a >> significant memory leak. > > Is valgrind able to expose this memory leak? > >>

Re: [BUG] memory leak with treads and stick-table/peers

On 6/5/19 3:06 PM, Emmanuel Hocdet wrote: Hi, Hi Emmanuel, After switched to haproxy 1.9 with threads activated, i noticed a significant memory leak. Is valgrind able to expose this memory leak? With threads disable (and bind process omitted) leak disappear. This seems to be related to