🐛 fix per-frame memory leak in raw callback dispatch - #78
Open
rayannott wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Raw callbacks (
on_receive_raw/on_send_rawon bothConnectionandServer) leaked amemoryview+bytesper dispatched frame: both references were created via the C API and never released. Replaced withpy::bytes, which owns and releases the reference.Measured at 150 msg/s for 60 s with an empty callback: 365 B/msg leaked before, 0 B/msg after;
tests/test.pypasses unchanged.Fixes #77