-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
blocking = hang #931
Comments
Related #726 . |
This is kind of expected... a blocking call (right now at least) cannot be interrupted. You set the max number of blocking threads to 10, so you can get 10 concurrent sleeps. Could you clarify what you would expect would happen in this case? |
You are right... I misunderstood what happened, the blocking behind was never executed because it was canceled by timeout and not because of I think I encountered the same problem with #726 on |
Version
Platform
Linux btw 4.20.8-arch1-1-ARCH #1 SMP PREEMPT Wed Feb 13 00:06:58 UTC 2019 x86_64 GNU/Linux
Subcrates
tokio-threadpool
Description
Unable to release blocking thread when a timeout occurs.Sometimes
blocking
will go into a bad state. Even if there is no blocking task is running, it is still alwaysNoCapacity
.https://gist.github.com/quininer/691caf86ec734dadc9d8590893825284
Note that this happens in hyper TokioThreadpoolGaiResolver @seanmonstar , which causes dns response to never return.
The text was updated successfully, but these errors were encountered: