OOM at secondary node of replication because of growing RSS

get source code:
#git clone -b bb-11.4-duckdb-jemalloc https://github.com/drrtuy/mdb-server.git
#cd mdb-server
#git clone --recurse-submodules https://github.com/MariaDB/duckdb-engine storage/duckdb/duckdb
#./storage/duckdb/duckdb/build.sh -D

(if you hit cryto related issue, hack
#sed -i 's/libxcrypt-dev/libcrypt-dev/g' /test-data/clones/mdb-server/storage/duckdb/duckdb/build.sh)

./storage/duckdb/duckdb/build.sh -S -t RelWithDebInfo or refer ./storage/duckdb/duckdb/build.sh -h

got to build folder and pack build
#cd /test-data/clones/DuckdbBuildOf_mdb-server
#cpack

refer: https://github.com/MariaDB/duckdb-engine – for building

1. setup 2 node async replication - 1 primary and 1 secondary
2. use sysbench-lua BMK (http://dimitrik.free.fr/blog/posts/mysql-perf-bmk-kit.html) , the reason I have taken BMK version of sysbench-lua and not https://github.com/akopytov/sysbench because we have 3 phases, table creations(create), data loading (prepare) and run
3. point primary and 1st run BMK's create , and then alter tables to have storage=duckdb
4. Run populate data ( prepare) and this will replicate data to secondary. Get highest gtid and wait on replica until this highest GTID replicated
5. stop sql_thread in secondary and the run sysbench test (update_key/nokey/write-only ) without autoincreament. pointing to primary and watch highest GTID of primary reached to relay-log of secondary
6. start sql_thread and you will see RSS growing and after 3/5 min OOM happened and you can check OOM ( dmesg -T |grep -i oom | tail -10)

Attaching all scripts