-
Notifications
You must be signed in to change notification settings - Fork 912
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
Intentionally leak thread_local CUDA resources to avoid crash (part 1) #16787
Merged
rapids-bot
merged 7 commits into
rapidsai:branch-24.10
from
kingcrimsontianyu:tianyu.liu/leak-intentionally
Sep 19, 2024
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
efb7f80
Intentionally leak thread_local CUDA resources
kingcrimsontianyu f3fac15
Improve implementation
kingcrimsontianyu 601e83d
Address reviewers comments
kingcrimsontianyu f323335
Cleanup
kingcrimsontianyu 5c28023
Add copy and move restrictions to the event wrapper
kingcrimsontianyu 3eef454
Merge branch 'branch-24.10' into tianyu.liu/leak-intentionally
vuule 5c19051
Merge branch 'branch-24.10' into tianyu.liu/leak-intentionally
vuule File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
issue (maybe): This means that every usage of
cuda_event
in the code base will leak the underlying event. Is this really what we want? Perhaps we only want to leak thethread_local
ones below.That is, should we change
event_for_thread
to do (approximately):?
Alternately, if the only usage of
cuda_event
is inevent_for_thread
, we could just delete this class completely and implementevent_for_thread
as:WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cuda_event
is only used as the RAII wrapper byevent_for_thread
, so deleting the user-defined destructor and allocatingcuda_event
on the heap happen to be equivalent. I agree that the leak makes thecuda_event
wrapper entirely superfluous, so I will use the alternative approach you suggested to make the code cleaner. Thank you @wence- !There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Completed