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.

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

Invoke AsyncJob continuations asynchronously #481

Merged
merged 1 commit into from
Oct 25, 2017
Merged

Conversation

yaakov-h
Copy link
Member

Fixes #480.

@yaakov-h yaakov-h added the bug label Oct 25, 2017
@yaakov-h yaakov-h added this to the 2.0.0 milestone Oct 25, 2017
@yaakov-h yaakov-h requested a review from voided October 25, 2017 09:19
Copy link
Member

@voided voided left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, my 7am brain didn't initially understand what it was looking at in the stack trace in #480.

I think it's unsafe to run continuations on the network thread, especially since consumer code might block on other operations (or deadlock like we see in #480). Must have been an oversight on my part from the original implementation of AsyncJobs.

leonard-thieu added a commit to leonard-thieu/SteamKit that referenced this pull request Oct 25, 2017
@yaakov-h yaakov-h merged commit 9677726 into master Oct 25, 2017
@xPaw xPaw deleted the fix/480-deadlock branch March 21, 2023 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants