Skip to content

Release SYNC FrameData in SynchronizationLayer.channelRead - #85

Open
netherguy4 wants to merge 1 commit into
RelativityMC:masterfrom
netherguy4:fix/release-sync-framedata
Open

netherguy4 wants to merge 1 commit into
RelativityMC:masterfrom
netherguy4:fix/release-sync-framedata

Conversation

@netherguy4

Copy link
Copy Markdown

One-line fix for #84: SynchronizationLayer.channelRead consumed each 0xFC SYNC FrameData and returned without releasing it (only the derived ByteBuf was released), tripping paranoid leak detection once per received SYNC.

The change adds packet.release() to the existing finally block, mirroring MetricsSynchronizationHandler.channelRead in the same package, which already releases its FrameData there.

Verified by reading the patched source and by bytecode inspection of a locally built jar (channelRead now calls FrameData.release; the unpatched published jar does not). No live reproduction beyond the leak-detector trace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant