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

All Blocking Primitives need to interact with Safepoint Logic #286

smarr opened this issue Jan 15, 2019 · 1 comment


1 participant
Copy link

commented Jan 15, 2019

For the blocking primitives, we need to decide one-by-one what to do with respect to safepoints.

There is always the potential for a deadlock, if they do not unregister before blocking.
Though, there may be performance implications that need to be considered.

This needs to be addressed so that #285 can be merged.

@smarr smarr added the bug label Jan 15, 2019

@smarr smarr added this to the v0.7.0 milestone Jan 15, 2019

@smarr smarr self-assigned this Jan 15, 2019

@smarr smarr added this to Open Issues in Completeness via automation Jan 15, 2019


This comment has been minimized.

Copy link
Owner Author

commented Feb 1, 2019

Got fixed with #288.

@smarr smarr closed this Feb 1, 2019

Completeness automation moved this from Open Issues to Completed Feb 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.