-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
deadlock when closing transport and/or server #4266
Comments
Interesting. Want to submit a fix? |
@marten-seemann Perhaps this? It's a bit dirty but it works:
|
This looks a bit complicated. I'd prefer something that doesn't use |
I agree that's better, breaking the loop will take some more digging to find a suitable fix. Will have a look at this further |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm noticing this semaphore deadlock which occurs occasionally, but not always:
I see that there are two orders that
mutex.Lock
can be called:When locking mutexes out of order, a deadlock can occur, which explains this deadlock (as far as I can tell):
The text was updated successfully, but these errors were encountered: