memory leak log during warmup phase

[fruch]

when using the following command, during a dtest:

cassandra-stress read n=100000 -mode cql3 simplenative -rate threads=1 -pop seq=1..100000 -node 127.0.33.1

we get this error about memory leakage, during the warmup:

Warming up READ with 25000 iterations...
ERROR [nioEventLoopGroup-2-1] 2024-07-31 14:33:29,852 ResourceLeakDetector.java:337 - LEAK: ByteBuf.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records: 
Created at:
	io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:402)
	io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:188)
	io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:179)
	io.netty.buffer.AbstractByteBufAllocator.ioBuffer(AbstractByteBufAllocator.java:140)
	io.netty.channel.DefaultMaxMessagesRecvByteBufAllocator$MaxMessageHandle.allocate(DefaultMaxMessagesRecvByteBufAllocator.java:120)
	io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:150)
	io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:788)
	io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:724)
	io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:650)
	io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:562)
	io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
	io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
	io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	java.base/java.lang.Thread.run(Thread.java:829)

[fruch]

seems to be related to the distro we select at the beginning.
I don't think we seen it since switching to debian

[CodeLieutenant]

seems to be related to the distro we select at the beginning. I don't think we seen it since switching to debian

I thinks it was not distro issue, but the JVM we used, firstly it was amazon distribution, but after some thought, I switched it to eclipse which has JDK and JRE, one for building, and latter for running, maybe the issue still persists, but its not visible to JRE.
I'll try to do some more investigation on it using amazon corretto to reproduce it and to try fixing it if it's real memory leak