fix: Proper release of the buffer obtained via PyObject_GetBuffer#2643
Merged
hoffstadt merged 1 commit intohoffstadt:masterfrom May 4, 2026
Merged
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
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.
name: Pull Request
about: Create a pull request to help us improve
title: Proper release of the buffer obtained via PyObject_GetBuffer
assignees: ''
Description:
This PR addresses an issue with the use of buffer protocol in DPG that was discovered in #2577 - see this comment. It does not fix the issue #2577 itself (we'll need to properly return
nullptrto get a correct exception there), but fixes the segfaults caused by incorrect release of a buffer that was never obtained.Concerning Areas:
None.