[knot-resolver-users] Re: Weird memleak since v6.0.9

Vladimir, Huge progress! During the night, our VM still on v6.0.8 crashed. Thankfully, exabgp did its job and the anycast went directly to another VM. This time, the second VM reached a memleak and rebooted (and the third took over the time the second restarted). You can see the the RAM usage increasing quite fast and VM1, then VM2, and generally, it is cleared in time to prevent a crash, except around 6 am.  Now, the good news is that we have identified the source :) We don’t know what the queries were, because it was DoH, but one of our customer was using this: https://github.com/0xERR0R/blocky As soon as he stopped using it, no more memleaks or sawtooth graphs. Sorry for the quick and dirty graph superposition below, but it shows the correlation: – the blue line is the the answer rate to this particular customer in pps, – in purple, it is the memory usage of the VM with knot resolver on it – before 10 am this VM was offline, so anything before is irrelevant.  The customer stopped his blocky around 10:40 (I believe he might have restarted it briefly between 10:50 and 11:35). So in our case, blocky was the culprit behind the knot resolver memleaks. The other knot resolver users experiencing memleaks should look if any requests are coming from a blocky instance. My next step will be to upgrade this VM and confirm that there are no memleaks anymore even with version > 6.0.8 and libknot15. All the Best, Gabriel