Hold onto the container after a get_property_ptr_ptr() call #20246
+352
−98
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.
Effects performed after a get_property_ptr_ptr() call may make the property pointer invalid by freeing or reallocating its container.
The container might be the object itself, the properties ht, a proxied object. For internal classes, this can be anything else.
Here we change the get_property_ptr_ptr handler so it exposes the actual container. The caller can then increase its refcount if any operation performed before the last access to the property could render the property invalid.
The get_property_ptr_ptr() implementation has the responsibility of ensuring that while the container's refcount is incremented, the property pointer remains valid.
Possible partial fix for GH-15938. Separate fixes are necessary for ASSIGN_DIM_OP, ASSIGN_OP, and references.
cc @iluuu1994 @nielsdos