Potential memory leak?

[Neubulae]

Describe the bug
After prolonged connection, the player eventually runs out of memory. The problem doesn't exist outside a Raknet connection, and, once the problem happens, it prevents player from further rejoining the server again with Raknet, only restarting the game works.

To Reproduce
Steps to reproduce the behavior:

1. Join server with Raknet
2. Idle
3. Gets kicked

Screenshots

Runtime info (please complete the following information):

• OS: Arch Linux
• Minecraft version: 1.18.2
• Mod version: alpha 4.16

Crash reports / logs
https://0x0.st/oQly.txt

Other mods
https://0x0.st/oQlt.txt

Checklist

• I am using the official version of the mod.
• I tried the latest development version but the issue persists.
• I searched for similar open issues and could not find an existing bug report on this.

[IAmSneak]

I've gotten the same issue in 1.19 versions using the official version of the mod and latest development. Also happens on the server with this log

[ishland]

Try reproduce with jvm flag -Dio.netty.leakDetection.level=advanced

[IAmSneak]

common mods:

• axes are weapons
• blastproof netherite
• carpet / extra / tis
• cloth config
• couplings
• fapi
• ferritecore
• krypton
• lazydfu
• lithium
• starlight
• raknetify (obviously)

[Neubulae]

As the log is extremely big I'll just paste it here https://0x0.st/oQhi.log

[ishland]

Try reproduce again with latest devbuild.

[Neubulae]

Try reproduce again with latest devbuild.

reproduces, do I need to provide a log again?

[ishland]

reproduces, do I need to provide a log again?

Yes definitely

[Neubulae]

it will take some time to reproduce a log, brb

[ishland]

Try reproduce with latest devbuild and provide logs if it still leaks.

[Neubulae]

the log is no longer spammed by things now so I think it's now fine? I'll wait and see

[Neubulae]

I don't reproduce with the latest build, thx pal.

[ishland]

Remember to remove the flag since the advanced leak detector comes with some performance overhead.