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.

Sign up for GitHub

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

Jump to bottom

[DOC] - RMM will not capture Out-of-Bound segfaults in pool mode #39

Closed
ogreen opened this issue Feb 4, 2019 · 4 comments · Fixed by #790
Closed

[DOC] - RMM will not capture Out-of-Bound segfaults in pool mode #39

ogreen opened this issue Feb 4, 2019 · 4 comments · Fixed by #790
Labels
doc Documentation inactive-30d

Comments

@ogreen
Copy link

ogreen commented Feb 4, 2019

When using RMM in pool mode, a problem could arise that out-of-bound memory segfaults will go undetected as the out-of-bound memory access will be within the bounds of the pre-allocated memory pool.

To avoid this, it is highly recommended that when developing code that the non-pool version of RMM be used until correctness has been verified at which case the pool can be used to improve performance.
@ogreen ogreen added the doc Documentation label Feb 4, 2019
@github-actions
Copy link

This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@github-actions
Copy link

This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.

@harrism
Copy link
Member

harrism commented Feb 16, 2021

In the future this should be fixed using new NVTX / sanitizer capabilities added to support memory pools.

@github-actions
Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@harrism harrism mentioned this issue Jun 1, 2021
Merged
@rapids-bot rapids-bot bot closed this as completed in #790 Jun 2, 2021
rapids-bot bot pushed a commit that referenced this issue Jun 2, 2021
@harrism
Document compute sanitizer memcheck support (#790)
37eac38 
Adds a section to README.md explaining incompatibility of most pool-based memory resources with memcheck, and noting that `cuda_async_memory_resource` and `cuda_memory_resource` are compatible with memcheck.

Fixes #39

Authors:
  - Mark Harris (https://github.com/harrism)

Approvers:
  - Jake Hemstad (https://github.com/jrhemstad)

URL: #790
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
doc Documentation inactive-30d
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Document compute sanitizer memcheck support [skipci] harrism/rmm
2 participants
@harrism @ogreen