[Bug] LEAK: ByteBuf.release() was not called before it's garbage-collected.

[pkgonan]

Describe the bug I checked the memory leak error after changing from jasync r2dbc mysql to asyncer. Come to think of it, I remember that I tested using the mirromutth r2dbc library before and confirmed the same memory leak, and when I changed it to jasync, there was no memory leak. If this project were to use mirromutth as it is, it probably still has the same problem.

Environment

• Spring Boot
• Kotlin 1.8.22
• R2dbc spi 1.0.0
• R2dbc pool 1.0.0

Error Log(Sentry)

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:407)
    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:833)

[jchrys]

Tbh, I have no idea. It's been several years since the last release of dev.miku's version, and there have been several patches since then.

Since the launch of io.asyncer, there hasn't been any reported leakage or issues so far.