Zhen Wang

> Failed to get ahold of @ted-jenks, I'm pinging someone to take this over if you don't mind Thank you @ted-jenks for this work. I have submitted a new PR...

Maybe duplicate of #1818

> Maybe duplicate of #1818 Sorry, it looks like the error stack is different

> Could you help to look at this issue too? Sure, I will try to fix it later.

`ShuffleIndexResult` and `ShuffleDataResult` seem to be no longer used after release. Shall we set their internal buffer to null after release? cc @zuston

https://github.com/wForget/incubator-uniffle/blob/0c80d4d62315aeb5366f9d2154f861fd59a769aa/common/src/main/java/org/apache/uniffle/common/netty/buffer/NettyManagedBuffer.java#L62-L70 After adding the following log in NettyManagedBuffer, I got some related logs from https://github.com/wForget/incubator-uniffle/actions/runs/9676598458 and did not find any repeated calls. ``` [2024-06-26 09:03:18.227] [Executor task launch worker for...

> Could you add some logs in `HadoopShuffleReadHandler.readShuffleIndex` to get more infomation why it returned a freed `ByteBuf` whose size is not `0`? Or maybe this time it's not in...

I seem to have found two threads that repeatedly release it: ``` [2024-07-01 22:12:37.173] [netty-rpc-client-24-1] [WARN] PooledUnsafeDirectByteBuf.release - Check PooledUnsafeDirectByteBuf release empty [2024-07-01 22:12:37.173] [netty-rpc-client-24-1] [WARN] PooledUnsafeDirectByteBuf.release - netty-rpc-client-24-1 [2024-07-01...

> io.netty.buffer.PooledUnsafeDirectByteBuf@6d1c06f3 They seem to be the same object. `PooledUnsafeDirectByteBuf` seems to be reusable before release.