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.
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
task: Drop the join waker of a task eagerly when the JoinHandle gets dropped or the task completes #6986
base: master
Are you sure you want to change the base?
task: Drop the join waker of a task eagerly when the JoinHandle gets dropped or the task completes #6986
Changes from 3 commits
163d841
d457bbb
ef31f18
cea78d0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Does this test actually fail without this change? If
b
does not get polled quickly enough, there might not be a refcycle.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.
Hmm, during development and testing the test would reliably fail without the changes I made. But I guess you are right here that this was luck that it always failed when I expected it to fail. I can try to make the test more reliable.
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.
Hmm ... I guess it's a loom test which exercises all possible interleavings of multi-threaded code. But it would be good to verify that this actually hits all the cases we care about.
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.
Thinking more about it, I don't think this needs to be a loom test. If you fix the issue with
b
getting polled quickly enough, change the runtime to a current-thread runtime so there's no threading to worry about, and move it to a normal test, that should be fine. Memory leaks are detected by both the valgrind and miri CI jobs, so that is enough to detect that the cycle does not cause a memory leak.That said, I think there's a different loom test that is good to have: