Fix: ArrayPool buffer leak in PatriciaTree Get methods #9322
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
ArrayPoolbuffer leak inGet()method - MovedArrayPool<byte>.Shared.Return(array)from try block to finally block to ensure cleanup even whenTrieExceptionis thrownGetNodeByKey()method - MovedArrayPool<byte>.Shared.Return(array)from try block to finally block to ensure cleanup even whenTrieExceptionis thrownTo give a little bit more detail about the why, the
Get()andGetNodeByKey()methods in PatriciaTree rent buffers fromArrayPoolbut only returned them in the success path.When
GetNew()throws aTrieException, the rented buffers weren't returned to the pool, it could've cause gradual memory pressure under sustained load (even if the array get GC'ed at some point).This was only affecting RPC endpoints when handling requests with keys larger than the 64byte stack allocation min.
For the p2p path, the peer would be banned before causing any significant harm.