Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

grpc-js: Stop leaking freed message buffer placeholder objects #2372

Merged

Conversation

murgatroid99
Copy link
Member

This fixes #2371. Currently, in a retrying call, when a message that has been sent is no longer needed, its entry in the message buffer is replaced with a placeholder entry with entryType="FREED". This frees up the memory of the actual message contents, but in a long-running stream, the placeholder entries themselves can pile up and start to use a significant amount of memory.

With this change, the message buffer only contains the range of messages that still need to be sent, and the new writeBufferOffset field indicates the offset the buffer has from the beginning of the message stream. The code still tracks message indices relative to the start of the message stream, because that can always just be incremented without any concern for the current state of the buffer.

@murgatroid99 murgatroid99 merged commit 07288b3 into grpc:@grpc/grpc-js@1.8.x Feb 24, 2023
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.

None yet

2 participants