Provide additional debug information when there is a memory leak (Reactor Netty client)

Hi,

Netty provides the following API

io.netty.buffer.ByteBuf.touch()


    /**
     * Records the current access location of this object for debugging purposes.
     * If this object is determined to be leaked, the information recorded by this operation will be provided to you
     * via {@link ResourceLeakDetector}.  This method is a shortcut to {@link #touch(Object) touch(null)}.
     */
    ReferenceCounted touch();

Currently Reactor Netty is the last component that records access to the byte buffers.
It will be very helpful if the Spring Gateway implementation uses this functionality when it does additional transformations of the content or buffers the object.
If there is a memory leak, when Netty dumps the stack traces of the components that accessed this object, it will be easier to find where the buffer was leaked.

Thanks,
Violeta

Start by locating the Reactor Netty client paths where Spring Gateway transforms or buffers content, then review how Netty ByteBuf.touch() and ResourceLeakDetector expose access locations. Done means the relevant Gateway buffer accesses are recorded so leak stack traces identify those transformations more clearly.