-
Notifications
You must be signed in to change notification settings - Fork 548
Fix for 1693 bug access to deleted memory in array proxy index #3600
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
Open
christophe-murphy
wants to merge
10
commits into
master
Choose a base branch
from
1693-bug-access-to-deleted-memory-in-array_proxy-index
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Fix for 1693 bug access to deleted memory in array proxy index #3600
christophe-murphy
wants to merge
10
commits into
master
from
1693-bug-access-to-deleted-memory-in-array_proxy-index
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
…nce index to ensure it is kept.
umar456
reviewed
Feb 4, 2025
OK, I reran address sanitizer on the CUDA backend with the following options and it ran without any issues reported: |
… for memory leaks.
I have done some more testing, see latest commit. I ran these through the leak sanitizer for all back ends and, aside from an unrelated memory leak in the random number generator engine, there are no issues. |
The copy constructors for array_proxy have been made private. This will prevent you from assigning an array proxy to an auto variable accidently. Array proxies should only be assigned to variables of type array. Assigning to an auto will now lead to a compilation error.
edwinsolisf
previously approved these changes
Mar 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Arrays can now be used as an index for creating an array proxy without failure.
Description
When using an array as an index when creating an array proxy a temporary index object is created and passed to the constructor for the array proxy. However the array underlying the index was not being kept after the temporary index was destroyed, resulting in undefined behavior. This fix ensures that the array is retained until the array proxy is destroyed. Users can now use an array as an index when creating an array proxy without needing to explicitly define an index object.
Fixes: #1693
Checklist