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.

Sign up for GitHub

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

Jump to bottom

Potential deadlock in proxy_registry #880

Closed
Neverlord opened this issue Aug 15, 2019 · 0 comments · Fixed by #881
Closed

Potential deadlock in proxy_registry #880

Neverlord opened this issue Aug 15, 2019 · 0 comments · Fixed by #881
Labels
bug
Milestone
0.17.1

Comments

@Neverlord
Copy link
Member

When using a deterministic setup, calling proxy_registry::erase can end up calling proxy_registry::erase again, because kill_proxy then runs inline. I'm not 100% sure whether this can also happen with a regular scheduler, but we should fix the deadlock in any case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
0.17.1
Development

Successfully merging a pull request may close this issue.

Fix potential deadlock in proxy_registry actor-framework/actor-framework
1 participant
@Neverlord