Fix reference leak in query cursor progress callback - #489
Merged
ObserverOfTime merged 1 commit intoAug 2, 2026
Merged
Conversation
query_cursor_progress_callback() leaked the Python callback's return value since PyObject_IsTrue() reads the object but does not consume the reference. The result is now decref'd after computing the truth value. Fixes tree-sitter#484
Member
|
Thank you for the contributions. |
Contributor
Author
|
Thank you for reviewing and merging the fix. I appreciate your time and look forward to contributing again. |
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
2 participants
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.
query_cursor_progress_callback() leaked the Python callback's return value since PyObject_IsTrue() reads the object but does not consume the reference. The result is now decref'd after computing the truth value.
Fixes #484