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

Consider - Weak SyncManager references to aid in deadlock detection #9

Open
ppervink opened this issue Feb 3, 2019 · 1 comment
Open

Consider - Weak SyncManager references to aid in deadlock detection #9

ppervink opened this issue Feb 3, 2019 · 1 comment
Assignees
@ppervink
Labels
enhancement New feature or request

Comments

@ppervink
Copy link
Owner

ppervink commented Feb 3, 2019

When implementing deadlock detection, consider tracking weak references in a static list to aid in detection across SyncManager instances.

Whether or not this gets implemented depends on impact to performance, which depends how it'll be used, synchronized (must be thread safe), and structured (must have minimal impact to both speed and memory usage).
@ppervink ppervink self-assigned this Feb 3, 2019
@ppervink ppervink added the enhancement New feature or request label Feb 3, 2019
@ppervink
Copy link
Owner Author

ppervink commented Feb 3, 2019

This is separate from deadlock detection in that it can (and would almost have to) come later.
I'm also not entirely sure this is something desired (or why have multiple sync managers). It may also be impractical to implement this. All TBD and separate from detecting (within one SyncManager) a deadlock.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ppervink ppervink

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ppervink