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

IECoreCycles : Use intrusive_ptr where appropriate #6098

Merged
merged 1 commit into from
Oct 17, 2024

Conversation

johnhaddon
Copy link
Member

All these functions allocate and return new data, so should assign to a Ptr to take ownership from the word go, and then return a Ptr to pass ownership to the caller. As it happened, all the existing callers were assigning the result to a Ptr anyway, but this did leave open a window during which an exception would result in a memory leak.

All these functions allocate and return new data, so should assign to a `Ptr` to take ownership from the word go, and then return a `Ptr` to pass ownership to the caller. As it happened, all the existing callers were assigning the result to a Ptr anyway, but this did leave open a window during which an exception would result in a memory leak.
@johnhaddon johnhaddon self-assigned this Oct 17, 2024
@murraystevenson murraystevenson merged commit 19bf576 into GafferHQ:main Oct 17, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Pending release
Development

Successfully merging this pull request may close these issues.

2 participants