With MALLOC_CONF="junk:true" env variable, Flamethrower (122d80f) takes all the available memory - 7-8 GB in our case - and gets OOM-killed on FreeBSD 13.5. See https://gitlab.isc.org/isc-projects/bind9/-/jobs/6568975.
This is how we start it: flame --dnssec -P udp -F inet -g file -f $qfile -Q 10000 -p 5030 -v 99 $address (protocol could also be DoH, DoT, or TCP; family inet6 - it does not matter).
In our CI, this issue occurs on FreeBSD 13.5, but not on Fedora 43. The likely reason is that on FreeBSD, jemalloc is the default allocator and takes into account the MALLOC_CONF setup. In contrast, on Fedora, the variable only affects BIND 9, which is compiled and linked with jemalloc, but Flamethrower is not.
With
MALLOC_CONF="junk:true"env variable, Flamethrower (122d80f) takes all the available memory - 7-8 GB in our case - and gets OOM-killed on FreeBSD 13.5. See https://gitlab.isc.org/isc-projects/bind9/-/jobs/6568975.This is how we start it:
flame --dnssec -P udp -F inet -g file -f $qfile -Q 10000 -p 5030 -v 99 $address(protocol could also be DoH, DoT, or TCP; family inet6 - it does not matter).In our CI, this issue occurs on FreeBSD 13.5, but not on Fedora 43. The likely reason is that on FreeBSD, jemalloc is the default allocator and takes into account the
MALLOC_CONFsetup. In contrast, on Fedora, the variable only affects BIND 9, which is compiled and linked with jemalloc, but Flamethrower is not.