-
Notifications
You must be signed in to change notification settings - Fork 37
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
Fix dropping TLS for detached futures #139
Merged
Merged
Changes from all commits
Commits
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,4 @@ | ||
use futures::task::{FutureObj, Spawn, SpawnError, SpawnExt as _}; | ||
use futures::{try_join, Future}; | ||
use shuttle::sync::{Barrier, Mutex}; | ||
use shuttle::{check_dfs, check_random, future, scheduler::PctScheduler, thread, Runner}; | ||
|
@@ -385,3 +386,28 @@ fn is_finished_on_join_handle() { | |
None, | ||
); | ||
} | ||
|
||
struct ShuttleSpawn; | ||
|
||
impl Spawn for ShuttleSpawn { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Nice - didn't know about the |
||
fn spawn_obj(&self, future: FutureObj<'static, ()>) -> Result<(), SpawnError> { | ||
future::spawn(future); | ||
Ok(()) | ||
} | ||
} | ||
|
||
// Make sure a spawned detached task gets cleaned up correctly after execution ends | ||
#[test] | ||
fn clean_up_detached_task() { | ||
check_dfs( | ||
|| { | ||
let atomic = shuttle::sync::atomic::AtomicUsize::new(0); | ||
let _task_handle = ShuttleSpawn | ||
.spawn_with_handle(async move { | ||
atomic.fetch_add(1, Ordering::SeqCst); | ||
}) | ||
.unwrap(); | ||
}, | ||
None, | ||
) | ||
} |
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.
Why are we still polling the future if execution already finished?
Was the task's local storage already dropped in
ExecutionState::cleanup
when we drained tasks?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.
We're not re-polling the future after execution finishes. But at
ExecutionState::cleanup
time, we drop the continuation, which for unfinished tasks involves resuming the task so that it can unwind its stack. That's how we end up in this code. We do still clean up the task's local storage inExecutionState::cleanup
, so this change isn't actually leaking anything, just changing where the cleanup happens.